Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by anegash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_geographic_performance

Get a breakdown of Google Ads performance by geographic location for a given customer ID and date range, enabling analysis of campaign results across different areas.

Instructions

Get performance breakdown by location

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": {
      "customerId": "<customerId>"
    },
    "name": "get_geographic_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateRangeNoLAST_30_DAYS
customerIdYesGoogle Ads customer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden. It provides no behavioral details such as data scope, metrics included, whether it is read-only, pagination, or any side effects. The verb 'get' only repeats the tool name without adding context.

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

Conciseness2/5

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

The description is a single short sentence, but it is under-specification rather than effective conciseness. It lacks essential details and does not earn its place by adding value beyond the tool name.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and minimal annotations, the description should explain return values and behavioral expectations. It provides none, making the tool ambiguous and hard to use correctly among many similar reporting tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention any parameters. Schema coverage is only 50% (customerId described, dateRange not), and the description adds no meaning beyond the schema. It fails to explain what dateRange controls or how customerId is used.

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 clearly states the tool gets performance data broken down by location, using a specific verb and resource. It distinguishes from campaign-level performance tools but does not explicitly differentiate from similar geographic tools like get_geographic_report or get_location_insights.

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 guidance on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent to guess based on the name alone.

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

Deploy Server

Other Tools