Skip to main content
Glama

Campaign details

campaign_details
Read-only

Retrieve full setup and performance for one Google Ads campaign: serving status and reasons, budget, bidding, targeting, assets, ad group results, and impression share lost to budget or rank.

Instructions

One campaign's setup and results in one call: status and why it isn't serving, budget, bid strategy and targets, networks, start/end, locations by name (with radius and exclusions), languages, ad schedule, location mode, negative keywords and shared negative lists, sitelinks/callouts/call assets, conversion goals it bids on, its ad groups with results, and search impression share lost to budget and rank.

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": {
      "customer_id": "<customer_id>",
      "campaign_id": "<campaign_id>"
    },
    "name": "campaign_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending yesterday
campaign_idYescampaign_id from account_overview
customer_idYesGoogle Ads customer ID, with or without dashes (from list_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.46.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context that the response is a broad diagnostic snapshot including 'why it isn't serving' and impression-share loss attribution. It stops short of noting response size, latency, or that unlisted fields are omitted.

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?

It is a single long sentence, but the core claim ('One campaign's setup and results in one call') is front-loaded and the rest is a dense, non-redundant enumeration of returned fields. The comma-list is heavy yet every item carries information, so it earns its length despite being hard to scan.

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 description effectively doubles as return-value documentation and covers the field families an agent would need to know about. Combined with a simple three-parameter schema and clear read-only annotations, an agent has enough to call it correctly; only explicit routing guidance against siblings is absent.

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 100%, with the days parameter already documented as a look-back window ending yesterday and campaign_id/customer_id sourced from sibling tools. The description adds no additional meaning about parameter behavior, so the baseline of 3 applies.

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 resource (one campaign) and explicitly frames the tool as a consolidated setup-plus-results read, then enumerates the exact field families returned (budget, bid strategy, locations, negative keywords, ad groups, impression share lost to budget/rank). This makes it distinguishable from account-level tools like account_overview and from report-style siblings such as keywords_report.

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: 'in one call' suggests this replaces several narrower lookups, and the schema notes campaign_id comes from account_overview, which hints at a drill-down flow. There is no explicit when-to-use/when-not statement or named alternative for campaign-level reporting versus run_gaql.

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