Analyze campaign CTR and CPC to recommend Facebook ad budget shifts and reallocate spend toward higher-performing campaigns.
Suggest budget shifts based on campaign CTR and CPC.
| Name | Required | Description | Default |
|---|---|---|---|
| date_preset | No | last_30d | |
| 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 must carry the full behavioral burden. It indicates the tool produces suggestions based on CTR and CPC, implying a read-only recommendation, but it does not explicitly state that no changes are made, what account scope is used, or whether authentication or specific permissions are required.
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 a single, front-loaded sentence with no wasted words. It is efficient, though its extreme brevity leaves little room for necessary context.
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?
An output schema exists, so return values need not be explained. However, the description omits prerequisites, scope, and any mention of the two input parameters, leaving significant gaps for an agent to call 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?
The schema has 0% description coverage for two parameters, date_preset and ad_account_id, and the description does not mention either one. CTR and CPC are not parameters, so no parameter meaning is added beyond what the schema names provide.
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 states a specific verb and resource: suggesting budget shifts. It also names the basis (campaign CTR and CPC), which helps an agent understand the tool's core function. However, it does not differentiate this tool from adjacent siblings like get_account_opportunity_recommendations or analyze_campaign.
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?
There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, whether it analyzes existing campaigns or requires prior setup, or what happens after suggestions are returned. Usage context is only implied by the verb 'suggest'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.