Skip to main content
Glama

ADS Beast

prepare_ad_create

Prepare a new ad inside an existing campaign: a responsive search ad on Google (headlines, descriptions, final_url) or a single-image ad on Meta (headline, body). Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaign_id": "<campaign_id>",
      "name": "<name>",
      "reason": "<reason>"
    },
    "name": "prepare_ad_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoMeta: primary text, up to 125 characters.
nameYesName shown in the interface.
reasonYesWhy, with numbers (shown to the approver).
headlineNoMeta: headline, up to 40 characters.
final_urlNoLanding page URL.
headlinesNoGoogle: 3-15 headlines, 30 characters each.
campaign_idYesADS Beast id from list_campaigns, not the platform's.
descriptionsNoGoogle: 2-4 descriptions, 90 characters each.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries meaningful extra burden and does it well: "Changes nothing" clarifies that no platform-side mutation occurs, while the preview_id with a 15-minute TTL and single-use constraint is exactly the operational behavior an agent needs before chaining into execute_prepared_change. It also implicitly reconciles readOnlyHint=false by showing the only persisted artifact is a short-lived preview token.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the operation, the variant options, and the non-mutating guarantee front-loaded, followed by the follow-up action. No filler, no restatement of the tool name, and the highest-value constraint (nothing changes) is not buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters at full schema coverage and no output schema, the key gap the description must close is what the call returns and how long it stays valid; the preview_id TTL and single-use note cover that. Combined with the per-platform parameter grouping and the handoff to execute_prepared_change, an agent has everything needed to prepare and then execute correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds conditional relevance the schema only hints at: it groups headlines/descriptions/final_url under Google and headline/body under Meta, telling the agent which parameters apply to which variant. A few fields (name, reason, campaign_id) are left to the schema alone, which is why this is not a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Prepare a new ad inside an existing campaign") and then enumerates the two concrete shapes it produces: a Google responsive search ad with headlines/descriptions/final_url and a Meta single-image ad with headline/body. That level of specificity lets an agent tell which variant it is building and routes it away from the execute step by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the workflow boundary explicitly: this call only stages the change, and execution happens via the named sibling execute_prepared_change. It does not spell out when a caller should prefer a different preparation tool (e.g. a Meta ad-set creation), but the two-step intent is unambiguous and the alternative at the execution stage is named outright.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.