Skip to main content
Glama

Account overview

account_overview
Read-only

Review campaign spend, clicks, conversions, and cost per conversion over a set window, plus flags for disapproved ads, stalled conversions, bid changes, and policy issues.

Instructions

Spend, clicks, conversions and cost per conversion per campaign over a window, plus attention when something needs a look: disapproved ads, Google's recommendations, conversions that stopped or went quiet, short calls not counted, keyword URLs overriding the ad's, recent bid strategy changes, and wording attorney advertising rules restrict.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • removedInput schema / properties / confirm_switch
      Removed value: -{
      -  "description": "Only after the user has agreed to spend their plan's account switch (a call answered \"Account switch:\"). Leave out otherwise",
      -  "type": "boolean"
      -}
  2. Changed1 schema field changedv0.14.1
    • addedInput schema / properties / confirm_switch
      Added value: +{
      +  "description": "Only after the user has agreed to spend their plan's account switch (a call answered \"Account switch:\"). Leave out otherwise",
      +  "type": "boolean"
      +}
  3. First observedv0.11.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the `attention` block appears conditionally, and it enumerates exactly which conditions trigger it (disapprovals, stopped conversions, unattributed short calls, URL overrides, bid strategy changes, legal wording restrictions). It does not state whether `attention` is a separate field or omitted entirely when empty, which would have been a useful final detail.

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?

Metrics are front-loaded in the opening clause, with the conditional `attention` content deferred to a second clause, which is the right information hierarchy. The attention enumeration is long but each item is a distinct signal, so little is wasted, though the single run-on sentence is denser than ideal.

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

Completeness5/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 carries the full burden of describing return content, and it does so: the four headline metrics, the per-campaign granularity, and the full taxonomy of attention signals. For a two-parameter read-only tool with annotations covering safety, nothing material is missing.

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 both `days` (1-365, default 30, ending yesterday) and `customer_id` (with or without dashes, sourced from list_accounts) fully documented in the schema. The description only adds the loose notion of 'a window', which the schema already specifies more precisely. Baseline 3 applies.

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 names the specific metrics returned (spend, clicks, conversions, cost per conversion) and the aggregation level (per campaign) over a time window, plus a conditional diagnostic section. That is far more concrete than a restated title, though it never names a sibling tool to contrast against, so differentiation from analytics_report or run_gaql is left to the agent.

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 phrase 'when something needs a look' implies this is the tool to reach for to triage account health, and the attention list hints at what it surfaces. There is no explicit 'use this instead of X' or stated preconditions, so an agent must infer fit relative to the reporting siblings.

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