Skip to main content
Glama

Campaign drafts

campaign_drafts
Destructive

Manages unpublished workspace campaign drafts. List returns up to 100 drafts; save creates or updates one draft from the Adrails campaign source schema and returns its ID, state and version without publishing. validate checks a saved draft; campaigns_publish_draft publishes a validated draft after its own approval. Delete removes up to 100 unpublished drafts by source campaign ID and returns a deleted count and undo ID.

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": {
      "input": "<input>"
    },
    "name": "campaign_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds genuinely useful behavior: save 'never publishes ads' and returns ID, state and version, delete reports deleted count and an undo ID (reversibility). It does not contradict the destructive hint, but it also doesn't spell out permission requirements or what happens on a failed validate.

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?

Four dense sentences, one per operation, with the overall scope front-loaded and the no-publish guarantee placed where it matters. No filler or restated title.

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

Completeness4/5

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

For a four-operation multiplexed tool with no output schema, the description covers what each operation does and what it returns (ID/state/version, deleted count and undoId). It leaves out what validate actually returns and the idempotencyKey requirement for mutations, which is only in the schema.

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 coverage is 75%, so most parameters are already documented, including the idempotencyKey and adAccountId semantics. The description adds operational limits (list up to 100, delete 1–100 source campaign IDs) but no extra meaning for draftId or source beyond what the schema says.

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?

Each of the four operations is stated with a concrete verb and resource: list drafts, save a draft from the Adrails campaign source schema, validate a saved draft, delete unpublished drafts by source campaign ID. The scope boundaries (unpublished workspace drafts, save never publishes) are explicit, so the agent can tell this apart from a publishing or setup tool.

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?

The description routes the agent through the intended workflow: save, then validate, then campaigns_publish_draft (which 'publishes a validated draft after its own approval'), with delete as the discard path. It stops short of stating when to use this versus sibling draft/creation tools such as campaign_templates or campaigns_setup.

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.