Skip to main content
Glama
Sign In
google-ads-mcp

google-ads-mcp

by eneelkant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_keyword_performance_report

Read-only

Get keyword-level performance metrics for Google Ads campaigns. Filter by campaign, ad group, or date range for targeted insights.

Instructions

Get keyword-level performance metrics.

Args: customer_id: Google Ads customer ID. campaign_id: Optional campaign filter. ad_group_id: Optional ad group filter. date_range: Date range (predefined or 'YYYY-MM-DD,YYYY-MM-DD'). limit: Max rows (default 100).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
date_rangeNoLAST_30_DAYS
ad_group_idNo
campaign_idNo
customer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Get' wording is consistent with those annotations. However, the description adds little behavioral context beyond that, such as pagination behavior, data freshness, or what the returned report contains.

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

Conciseness5/5

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

The description is compact and well-structured: a one-line purpose followed by a clear parameter list. Every sentence adds useful information and there is no redundant or marketing-style filler.

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?

For a read-only report tool, the description plus schema and annotations is mostly complete: all parameters are documented and the intent is clear. The main gap is that the exact metrics returned are not specified and the relationship to the similarly named get_keyword_performance tool is not clarified.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden of explaining parameters. It does this well by describing all five parameters, including optionality, the date range format, and the limit default, which is essential for correct invocation.

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 states a clear action ('Get') and a specific resource ('keyword-level performance metrics'), so an agent can identify it as a read-only reporting tool. However, it does not distinguish this tool from the sibling get_keyword_performance, which sounds nearly identical and could easily be confused with it.

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?

The description provides no guidance on when to choose this tool over alternatives such as get_keyword_performance, get_campaign_performance, or get_search_terms_report. It only lists parameters and filters, leaving the selection decision entirely to the agent.

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