Create ONE campaign with MULTIPLE ad sets and MULTIPLE ads each (1 campaign -> N ad sets -> M ads), image or video, including DPA/Catalog dynamic product ads. Created PAUSED. Honors spend guardrails. Pro feature. WRITES live.
| Name | Required | Description | Default |
|---|---|---|---|
| campaigns | Yes | One or more structured campaigns (usually one). | |
| meta_account_id | No | Ad account (defaults to primary). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds significant behavioral context beyond the readOnlyHint annotation: campaigns are created PAUSED, respects spend guardrails, is a pro feature, and writes live data. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is exceptionally concise: two sentences front-loading the core structure, then additional key details (PAUSED, guardrails, pro feature). Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (nested schemas) and no output schema, the description covers the primary structure and constraints. It does not explain error behavior or guardrail limits, but overall is sufficient for an agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the description does not need to repeat parameter details. The description mentions image/video and DPA, but these are already covered in the schema. No additional semantic depth beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool creates ONE campaign with multiple ad sets and multiple ads, specifying supported types (image, video, DPA/catalog). The verb 'Create' and resource 'structured campaign' are explicit, distinguishing it from simpler or bulk creation tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for complex campaign structures (1:N:M) and includes DPA support. It notes the campaign is created PAUSED and honours spend guardrails, but does not explicitly state when to use this tool vs. alternatives like 'create_campaign' or 'bulk_create_campaigns'. Still, context from sibling tools helps differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but creation tools (create_campaign, bulk_create_campaigns, create_structured, add_ad_to_adset) overlap in scope, potentially causing misselection. However, descriptions clarify differences.
All tool names follow a consistent verb_noun pattern in snake_case, such as 'bulk_create_campaigns', 'get_insights', 'pause_campaigns'. No mixing of conventions.
23 tools cover the Meta Ads domain well, but the count is slightly high. Most tools are justified, though some could be merged (e.g., creation variants).
Core CRUD is covered for campaigns and ads, but there is no tool to create an ad set independently (only via create_structured). Creative editing and standalone ad set creation are missing, leaving notable gaps.