Skip to main content
Glama

ADS Beast

campaign_draft_edit

Low-level edit of a campaign draft before publishing: merge targeting keys, update ads, replace ad groups, rename, change goal, budget or UTM. Nothing is sent to the platform. Amounts are in the ad account's own currency, in whole units (not cents or micros).

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": {
      "client_id": "<client_id>",
      "build_id": "<build_id>"
    },
    "name": "campaign_draft_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName shown in the interface.
build_idYesDraft id from list_campaign_drafts.
ad_groupsNoFull replacement of the ad groups.
client_idYes
objectiveNoCampaign goal.
targetingNoTargeting keys to merge; a null value removes the key.
ad_updatesNoAd edits.
utm_paramsNoUTM parameters.
budget_typeNodaily or monthly.
budget_amountNoBudget in the account currency, whole units.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds genuinely new context by stating nothing is pushed to the platform, which is the key safety fact for a draft-editing tool. It also discloses the merge-vs-replace asymmetry in behavior via "merge targeting keys" and "replace ad groups," though it does not say what happens to omitted ad groups or ads beyond the full replacement note.

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

Conciseness4/5

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

Two sentences, front-loaded with the core purpose and the list of operations, followed by the critical no-side-effects and unit caveats. Dense and largely waste-free, though the operation list is a somewhat compressed run-on that could be grouped more scannably.

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

Completeness3/5

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

For a 10-parameter tool with nested objects and no output schema, the description covers what can be changed and the unit convention, but says nothing about what the tool returns or how merge conflicts/replacements are reported. That absence is a real gap given the nested ad_updates and full-replacement ad_groups semantics.

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

Parameters3/5

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

Schema description coverage is 90%, so the schema already carries most parameter meaning. The description's currency/whole-units note and merge semantics largely restate what the schema already documents ("Targeting keys to merge; a null value removes the key", "Budget in the account currency, whole units"), adding little beyond it.

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

Purpose4/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 ("low-level edit of a campaign draft") and enumerates the editable surfaces: targeting keys, ads, ad groups, name, goal, budget, UTM. It is easy to distinguish from read-only siblings like campaign_draft_details or get_campaign_draft, though it does not explicitly differentiate itself from update_campaign_draft.

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

Usage Guidelines3/5

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

The phrase "before publishing" and "Nothing is sent to the platform" establishes the context in which this tool applies, implying publish-check/publish tools come after. However, no explicit when-not guidance or named alternative (e.g., update_campaign_draft vs this low-level merge tool) is given, so the agent must infer the boundary.

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.