Create many Meta campaigns at once on ONE account (rate-limit-safe, validated). WRITES live. Honors plan limits, spend guardrails, and capacity. Auto-uses the correct Page/Instagram/pixel. Each campaign needs an imageUrl (public image, or Drive/Dropbox share link).
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | ||
| page_id | No | ||
| pixel_id | No | ||
| campaigns | Yes | ||
| catalogId | No | ||
| productSetId | No | ||
| meta_account_id | No | ||
| instagram_account_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation (false, indicating writes), the description adds 'WRITES live', 'rate-limit-safe, validated', and 'Honors plan limits, spend guardrails, and capacity'. This provides behavioral context not in annotations, though it could detail error handling.
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?
Three sentences, front-loaded with main purpose. Concise but could be structured better for readability.
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?
No output schema and complex bulk creation. Description mentions validation and limits but lacks explanation of return values, partial failure behavior, or full parameter details. Adequate but not thorough.
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?
With 0% schema description coverage, the description must compensate. It mentions imageUrl and its source types, and hints at auto-used Page/Instagram/pixel, but does not explain other top-level parameters (confirm, catalogId, etc.). The mention of imageUrl as needed contradicts the schema where it is not required.
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 'Create many Meta campaigns at once on ONE account', specifying the verb and resource. It distinguishes from sibling tools like 'create_campaign' (single) and 'bulk_create_multi_account' (multi-account) by emphasizing single account and bulk nature.
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?
It provides context on when to use: when creating multiple campaigns on one account, with assurances of rate-limit safety and validation. It implies but does not explicitly state when to use alternatives (e.g., single creation).
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.