Skip to main content
Glama

Ads report

ads_report
Read-only

Retrieve an account's ads with headlines, final URLs, ad strength, policy and approval issues, and performance results. Scope to the whole account, one campaign, or one ad group.

Instructions

The account's ads with their headlines and descriptions (pins and Google's performance labels), final URL, ad strength, approval and policy issues, why one isn't serving, and results in the window. Whole account, or one campaign or ad group.

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>"
    },
    "name": "ads_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending yesterday
limitNoAds to list, by cost
ad_group_idNoOnly this ad group (from campaign_details)
campaign_idNoOnly this campaign (campaign_id from account_overview)
customer_idYesGoogle Ads customer ID, with or without dashes (from list_accounts)
include_pausedNoAlso list paused ads

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.46.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description earns credit for disclosing what is actually returned — including diagnostic content like why an ad isn't serving and policy issues — which matters because there is no output schema. It says nothing about pagination behavior, volume, or API cost of an open-world query.

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 what the report contains and closed with the scope options. The field list is dense but each item is a distinct data point an agent would want to know; nothing is redundant with the name or 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?

With no output schema, the description needs to say what comes back, and it does so thoroughly for a read-only report; all six parameters are schema-documented. The remaining gap is operational: no hint about result size, whether the limit is cost-ranked (only in the schema), or how the open-world lookup behaves.

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%, so every parameter is already documented, and the baseline is 3. The description reinforces scope ('whole account, or one campaign or ad group') and the windowing notion ('results in the window'), but adds no syntax, ordering, or default details beyond the schema.

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?

Names a specific resource (the account's ads) and enumerates the payload: headlines/descriptions, final URL, ad strength, approval and policy issues, non-serving reasons, and performance. That is far beyond a restatement of the title, though it never contrasts itself with sibling reports such as keywords_report or analytics_report, so an agent must infer the distinction from the resource noun alone.

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 closing sentence 'Whole account, or one campaign or ad group' tells the agent the three valid scopes, which is real usage guidance, but there is no explicit when-to-use/when-not, no mention of the default 30-day window or the cost-ranked limit, and no routing to alternatives.

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