Google Ads MCP Server

get_auction_insights

Retrieve competitive analysis and auction insights for Google Ads campaigns. Identify performance benchmarks and competitor data to refine bidding strategies.

Instructions

Get competitive analysis and auction insights

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_auction_insights"
  }
}

Input Schema

Name	Required	Description	Default
`campaignId`	No	Optional campaign ID
`customerId`	Yes	Google Ads customer ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Since no annotations are present, the description carries the full burden of behavioral disclosure. It only states the action without mentioning data scope, required permissions, or limitations (e.g., auction insights may not be available for all campaigns), so the agent receives no safety or behavior hints.

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 a single, meaningful sentence with no redundant words. It is front-loaded and efficient, earning its place without any fluff.

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 low-complexity 2-parameter read tool, the description is minimally viable but somewhat vague. It does not specify what data will be returned or how to use the parameters effectively, and with no output schema or annotations, a bit more detail would improve completeness.

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?

The schema has 100% description coverage for its 2 parameters, so the baseline is 3. The description adds no extra meaning about how campaignId filters insights or why customerId is required, but the schema already covers these basics.

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 competitive analysis and auction insights, using a specific verb and resource. However, it does not differentiate from sibling insight tools like get_audience_insights or get_location_insights, missing the chance to clarify its unique scope.

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 guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, exclusions, or recommended scenarios, leaving the agent to infer usage from 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