Skip to main content
Glama
Sign In

Camberstack: Google Ads

by io.camberstack
OverviewDiscussionsAdmin

Account overview

account_overview
Read-only

Spend, clicks, conversions and cost per conversion per campaign over a window, plus attention when something needs a look: disapproved ads and why, Google's recommendations, primary conversions gone quiet.

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 changed
    • 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 changed
    • 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. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A3.5/5.0
Behavior4/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 safety is covered. The description goes beyond them by disclosing the return shape: per-campaign performance metrics plus a diagnostic `attention` block (disapproval reasons, recommendations, conversions gone quiet) — real value an agent can't get from the annotations.

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?

A single sentence, front-loaded with the primary metrics, with the exception/diagnostic part trailing after the colon. Every clause carries information, though the dense colon-list takes a moment to parse.

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 must convey what comes back, and it does: metric set, grain, window, and the three diagnostic categories. Minor gaps remain — whether results are rows per campaign, what the `attention` structure looks like, and any currency/aggregation caveats.

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 100% and the schema already explains `days` (1-365, default 30, ending yesterday) and `customer_id` (with or without dashes, from list_accounts). The description's 'over a window' only echoes this, adding no format or constraint detail 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?

It names a specific set of metrics (spend, clicks, conversions, CPA) at a stated grain (per campaign) over a window, and separately describes the `attention` section with three named diagnostics. It is clearly distinguishable from the raw-query sibling run_gaql and the analytics_* tools, but it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative named. The 'plus `attention` when something needs a look' clause describes output content, not selection guidance, so an agent must infer that this is a first-stop account summary rather than a targeted report.

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

All Camberstack: Google Ads toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources