Skip to main content
Glama

Campaigns structure

campaigns_structure
Read-onlyIdempotent

Reads, from the last sync, how an ad account's campaigns are built on any platform: every campaign with its type, status, budget and bidding; every ad group or ad set with its keywords (ids, match types, status, quality scores, review, and spend and conversions over the sync's days, the ones that spent most kept when a campaign is large) and, for Performance Max asset groups, each text with its asset id and the assets Google disapproved; for Shopping ad groups and Performance Max asset groups, the products their listing groups include and exclude, by brand, category, product type, custom label or item id; on Google, each campaign's own negative keywords, the shared negative lists it uses and the extensions Google holds back, and its controls: the portfolio strategy it bids with and the target actually in force with what sets it, Google's suggested budget, the placement exclusion and brand lists it uses, labels, ad schedule and device bid adjustments; at account level the portfolio strategies, every shared list with its first entries, what the account excludes and its user lists with their sizes; every ad with its format, headlines, descriptions, paths, final URL, pictures and review. On Meta, every ad set's tracking (destinationType, the conversion location: WEBSITE or ON_AD for an instant form; optimizationGoal; the datasetId and event it optimizes for) and every ad's urlParameters (null when it has none), finalUrl, leadFormId and the datasets its tracking reports to. Its ids are the ones meta_edit, google_ads_edit and google_ads_build take for existing entities. campaignId narrows it to one campaign.

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": "campaigns_structure"
  }
}

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. Changed3 schema fields changed
    • addedInput schema / properties / input / properties / campaignName
      Added value: +{
      +  "description": "Searches every account.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / input / required
      Removed value: -[
      -  "accountId"
      -]
    • 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

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior on top: results are a snapshot 'from the last sync' rather than live, keyword rows are truncated to the top spenders 'when a campaign is large,' and Meta urlParameters is 'null when it has none.' It also discloses Google-specific holds like disapproved assets and withheld extensions. Pagination, size ceilings and latency are still unstated, keeping it at 4.

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

Conciseness3/5

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

Almost every clause carries real information about the return surface, so the length is largely earned, and the read-plus-staleness qualifier is front-loaded. However, it is delivered as one enormous semicolon-chained sentence that an agent must parse linearly, with no grouping or headings for platform-specific versus account-level content.

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 and a deeply nested return, the description carries the burden and does so thoroughly, enumerating campaign fields, keyword fields, listing groups, negatives, bidding controls, and Meta tracking fields. Remaining gaps are operational: response size limits, pagination, and what an empty or unsynced account returns.

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 schema already documents accountIds, userStatement and idempotencyKey. The description's only added parameter meaning is that campaignId narrows the read to a single campaign and that account selection is workspace-bounded, which is modest incremental value. Baseline 3 is appropriate given the schema does most of the work.

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 opens with a specific verb and resource: 'Reads, from the last sync, how an ad account's campaigns are built on any platform,' then enumerates the hierarchy (campaigns, ad groups/ad sets, keywords, ads, account-level lists). An agent can immediately tell this is the structural read model rather than a mutation or setup tool. It never names or contrasts a sibling such as campaigns_setup or campaign_drafts, so it falls short of a 5.

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: 'campaignId narrows it to one campaign' tells how to scope, and 'Its ids are the ones meta_edit, google_ads_edit and google_ads_build take for existing entities' is a genuinely useful downstream hint that this is the ID source for edit calls. There is no explicit statement of when to reach for this versus campaigns_setup or campaigns_drafts, and no prerequisites or exclusions are given.

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.