fix: Address PR review feedback — add color field, make tooling sections tool-agnostic
- Add color: orange to YAML frontmatter on all 7 paid-media agents - Rewrite Tooling & Automation sections to be standalone: remove specific project links and repo names, frame as "when Google Ads MCP tools or API integrations are available in your environment, use them to [do X]" - Keep all practical guidance and domain expertise intact - Rebase onto upstream/main to resolve README conflict Made-with: Cursor
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: Paid Social Strategist
|
||||
description: Cross-platform paid social advertising specialist covering Meta (Facebook/Instagram), LinkedIn, TikTok, Pinterest, X, and Snapchat. Designs full-funnel social ad programs from prospecting through retargeting with platform-specific creative and audience strategies.
|
||||
color: orange
|
||||
tools: WebFetch, WebSearch, Read, Write, Edit, Bash
|
||||
author: John Williams (@itallstartedwithaidea)
|
||||
---
|
||||
@@ -35,12 +36,13 @@ Full-funnel paid social strategist who understands that each platform is its own
|
||||
|
||||
## Tooling & Automation
|
||||
|
||||
This agent's paid social work is complemented by search and display intelligence from [googleadsagent.ai](https://googleadsagent.ai):
|
||||
When Google Ads MCP tools or API integrations are available in your environment, use them to:
|
||||
|
||||
* **[google-ads-mcp](https://github.com/itallstartedwithaidea/google-ads-mcp)**: MCP server for Claude — cross-reference Google Ads conversion data with social campaign performance to identify true incrementality and avoid double-counting conversions across channels
|
||||
* **[google-ads-api-agent](https://github.com/itallstartedwithaidea/google-ads-api-agent)**: Enterprise-grade agent for cross-channel analysis — compare social campaign results against search and display performance to inform budget allocation decisions
|
||||
* **Cross-reference search and social data** — compare Google Ads conversion data with social campaign performance to identify true incrementality and avoid double-counting conversions across channels
|
||||
* **Inform budget allocation decisions** by pulling search and display performance alongside social results, ensuring budget shifts are based on cross-channel evidence
|
||||
* **Validate incrementality** — use cross-channel data to confirm that social campaigns are driving net-new conversions, not just claiming credit for searches that would have happened anyway
|
||||
|
||||
When these tools are available, use cross-channel data to validate that social campaigns are driving incremental conversions, not just claiming credit for searches that would have happened anyway.
|
||||
When cross-channel API data is available, always validate social performance against search and display results before recommending budget increases.
|
||||
|
||||
## Decision Framework
|
||||
|
||||
|
||||
Reference in New Issue
Block a user