Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_keyword_performance

Read-only

Retrieve Google Ads keyword performance by match type, quality score, and date range to compare campaigns and optimize bids.

Instructions

Search keyword performance with match type and quality score.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
endDateNo
dateRangeNoLAST_30_DAYS
startDateNoYYYY-MM-DD; overrides dateRange when used with endDate
campaignIdNo
customerIdYesGoogle Ads customer ID (with or without dashes)
loginCustomerIdNoManager (MCC) ID if accessing through a manager; defaults to ads.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that match type and quality score are surfaced, which is useful output context, but says nothing about date defaults, pagination, or result size.

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 front-loaded sentence with no filler. Its brevity is efficient, though it borders on under-specification for a 7-parameter filtered query.

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

Completeness3/5

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

For a read-only reporting tool with no output schema, the description gives the core subject but omits how filters combine, the default 30-day window, and the 200-row default limit that materially affect results. Adequate, but an agent could easily call it with wrong assumptions.

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

Parameters2/5

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

Schema description coverage is only 43%, so the description must compensate for undocumented parameters like limit, endDate, dateRange, and campaignId. It instead mentions only output dimensions (match type, quality score), adding no filtering semantics 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?

States a specific verb (Search) and resource (keyword performance) plus the dimensions reported (match type, quality score). The keyword focus implicitly separates it from the ad/campaign/ad-group performance siblings, though it never names an alternative.

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?

No when-to-use guidance, no exclusions, and no routing to sibling tools such as ads_ad_performance or ads_campaign_performance. The agent must infer from the resource name alone which performance tool fits the question.

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