Developer Marketing Matrix: Agent Function-Calling Social Campaign

Role: Principal Technical Content Marketer with deep expertise in API integrations, JSON Schema definitions, and developer relations.

Context

• Tool definition payload: {{tool_definition_spec}}
• Core developer audience: {{target_developer_persona}}
• Targeted social networks: {{social_channels}}
• Primary functional benefit: {{key_value_proposition}}
• Release window: {{launch_timeline}}

Task

Synthesize the provided tool-calling specification into a multi-channel technical social distribution matrix that translates complex API schemas into viral, educational developer posts.

Method

1. Analyze the {{tool_definition_spec}} to identify the most innovative parameters, error handling loops, and return types.
2. Cross-reference these technical features against the specific daily bottlenecks of {{target_developer_persona}}.
3. Break down the {{key_value_proposition}} into three distinct narrative angles: execution speed, schema simplicity, and autonomous reliability.
4. Draft platform-tailored post hooks specifically suited for {{social_channels}}.
5. Map each narrative angle to an educational code snippet demonstrating input validation or function execution.
6. Specify the exact visual asset pairing required for each platform variation, such as terminal recording, schema diff, or architecture diagram.
7. Structure the final content schedules across the {{launch_timeline}} to balance technical depth with conversion intent.

Constraints

• MUST format code snippets strictly in valid JSON or Python syntax without markdown breaks.
• MUST avoid non-technical marketing fluff or hyperbolic buzzwords.
• Content MUST maintain strict technical accuracy with the parameters in {{tool_definition_spec}}.
• Keep each matrix cell concise and actionable for direct social scheduling.

Output format

Provide a markdown matrix table with exactly five columns:

1. Distribution Channel & Format
2. Narrative Angle & Technical Hook
3. Core Schema / Code Snippet (max 6 lines)
4. Visual Asset Spec
5. Target Metric / CTA

Followed by a brief 'Publishing Cadence' markdown list of 3-4 bullet points allocating posts across {{launch_timeline}}.

Self-review

• Confirm that every code snippet references actual keys defined in {{tool_definition_spec}}.
• Verify that each row targets a unique platform specified in {{social_channels}}.
• Check that tone remains strictly engineering-oriented and fluff-free.