Skip to main content
Glama

ADS Beast

list_campaign_drafts

Read-only

Builds in the campaign builder, newest first, as summaries: name, platform, type, status (draft, ready, paused, launched), budget, how many ad groups, ads and keywords, whether an assistant created it, whether it was already published, and the cabinet link. A key bound to one client lists only that client's builds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_campaign_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoBuilds per page. A page is also cut to fit the response size limit; when the reply has has_more = true, call again with offset = next_offset.
offsetNoBuilds to skip; use next_offset from the previous page.
statusNo
client_idNoOnly this client's builds (id from list_clients).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered; the description adds genuine context beyond them: newest-first ordering, that results are summaries rather than full objects, the exact shape of the returned status enumeration, and — importantly — the tenancy rule that a client-bound key silently narrows results to one client. It does not discuss response-size truncation, but that lives in the limit parameter's schema text.

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 compact sentences with no filler, and the return-field inventory earns its length because no output schema exists. The lead clause is slightly less front-loaded than ideal — 'Builds in the campaign builder' delays the fact that this is a listing call.

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?

With no output schema, the enumerated return fields are essential and present, and pagination/truncation behavior is handled in the schema. The remaining gap is relational: it does not say how these summaries differ from campaign_draft_details or whether draft creation feeds this list, which matters given the dense sibling set.

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% and the limit/offset parameters already document page sizing, truncation and next_offset usage in detail, with status carrying an enum. The description contributes only the client_id tenancy nuance ('a key bound to one client lists only that client's builds'); it never mentions status filtering or how status values map to the listed set.

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 states the resource (campaign builds/drafts in the campaign builder) and precisely enumerates the summary fields returned (name, platform, type, status, budget, counts, assistant flag, published flag, cabinet link), plus the default sort ('newest first'). The verb is phrased awkwardly ('Builds in the campaign builder') rather than 'Lists', and no sibling such as campaign_draft_details is named, but an agent can still tell this is the summary-listing tool.

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?

Usage is only implied: 'as summaries' hints that a detail-oriented sibling (campaign_draft_details) exists, and the client-key sentence hints at scoped listing, but there is no explicit 'use this when' or 'do not use for X' statement. No alternative tool is named, so the agent must infer routing from sibling names alone.

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.