Creates a Facebook ad from an existing creative by linking an ad set, creative ID, and name; defaults to paused status.
Create ad from an existing creative.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| status | No | PAUSED | |
| adset_id | Yes | ||
| creative_id | Yes | ||
| ad_account_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden and fails. 'Create' implies a write/mutation, but no permissions, no side effects, no default-status implications (the schema default is PAUSED, invisible here). No mention of whether the ad is active immediately or what the return is.
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?
A single short sentence, front-loaded and waste-free. It is concise, though brevity here is achieved by omission rather than efficiency of a well-formed description.
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?
For a 5-parameter mutation tool with no annotations, no description coverage, and only a bare output schema, the definition is too thin. Required relationships, defaults, and behavioral context are all absent.
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 0% and the description adds no parameter meaning. It does not explain adset_id, creative_id, name, ad_account_id, or the significance of the PAUSED default. With 5 params and zero coverage, the description should compensate but does not.
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?
States a verb (Create) and resource (ad), but the qualifier 'from an existing creative' is the only differentiator. It does not clearly distinguish from siblings like create_ad_creative or update_ad. The purpose is understandable but leaves ambiguity about relationship to creative-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?
No when-to-use guidance, no alternatives named, no preconditions stated (e.g., that the creative must already exist). An agent has no explicit routing signal vs. create_ad_creative or create_campaign.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.