Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by anegash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_keyword_ideas

Generate keyword ideas for Google Ads by supplying a customer ID and seed keywords. Expand your campaign targeting with relevant suggestions.

Instructions

Get keyword suggestions and ideas

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>",
      "keywordSeed": "<keywordSeed>"
    },
    "name": "get_keyword_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYesGoogle Ads customer ID
keywordSeedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only states a basic action. It does not disclose whether the operation is read-only, requires specific permissions, returns paginated results, or has rate limits, so the agent has little insight into behavioral expectations.

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, concise sentence with no unnecessary wording. It is immediately front-loaded and easy to parse, earning full marks for conciseness.

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

Completeness2/5

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

The tool has no output schema and ambiguous parameter semantics, yet the description provides no context about expected results, use cases, or the purpose of the keywordSeed parameter. It is incomplete for an agent to invoke correctly.

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?

The schema partially covers parameters (customerId is described, keywordSeed is not), but the description adds no parameter meaning. Since schema_description_coverage is only 50%, the description should compensate for the missing keywordSeed semantics but does not.

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 verb ('Get') and resource ('keyword suggestions and ideas'), which conveys the tool's basic purpose. It distinguishes from sibling 'get_keywords' via the term 'ideas', but does not explicitly differentiate from other suggestion-related tools.

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 vs alternatives such as 'get_keywords' or 'generate_forecast_metrics'. There are no examples, prerequisites, or exclusions, leaving the agent to guess the appropriate context.

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