Samuelz® Marketing

Keyword-Nachfrage recherchieren

get_keyword_research

Read-onlyIdempotent

Read approximate Google Keyword Planner monthly search volumes, advertising competition and account-currency CPC/bid ranges for the exact connected Google Ads account. Requires marketing:read and current Marketing/account authority. Supply languageCode, countryCodes and inclusive monthRange explicitly. mode=historical needs up to20keywords; mode=ideas uses keywords, a public HTTPS seedUrl (including a competitor website), or both. Follow nextCursor with identical inputs. Close variants, missing months/keywords and coverage remain explicit. Website ideas are not evidence of a competitor ranking; advertising competition is not organic difficulty. Does not create keyword plans, campaigns or budget writes; no additional model call. POST /api/v1/tenant/read/get_keyword_research.

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": {
      "connectionId": "<connectionId>",
      "languageCode": "<languageCode>",
      "countryCodes": "<countryCodes>",
      "monthRange": "<monthRange>"
    },
    "name": "get_keyword_research"
  }
}

Input Schema

Name	Required	Default
`mode`	No	historical
`limit`	No
`cursor`	No
`seedUrl`	No
`keywords`	No
`monthRange`	Yes
`connectionId`	Yes
`countryCodes`	Yes
`languageCode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses permission requirements, exact-account scope, cursor behavior with identical inputs, and caveats that close variants and missing coverage remain explicit. It also clarifies interpretation limits: website ideas are not evidence of a competitor ranking, and advertising competition is not organic difficulty.

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?

The core purpose is front-loaded and the dense sentences mostly carry useful operational details. Some clauses are telegraphic and could be easier to scan, but there is little wasted text for a nine-parameter tool.

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

Completeness5/5

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

Although there is no output schema, the description explains the returned data types, account scope, pagination behavior, mode constraints, permissions, and important interpretation caveats. It gives an agent enough context to call the tool correctly and understand its boundaries.

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

Parameters4/5

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

With zero schema description coverage, the description compensates for key parameters by explaining mode requirements, up-to-20 keywords for historical mode, seedUrl alternatives for ideas mode, inclusive monthRange, and cursor reuse. It still leaves limit, connectionId, and country-code cardinality without added meaning, so it is strong but not fully complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: reading Google Keyword Planner monthly search volumes, advertising competition, and CPC/bid ranges for the exact connected Google Ads account. It is clearly distinguishable from planning or campaign-write tools and gives a precise scope an agent can select on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit prerequisites, required inputs, mode-specific conditions for historical versus ideas, and states what the tool does not do (no keyword plans, campaigns, budget writes, or extra model call). It lacks explicit named alternatives, but the mode guidance and exclusions are strong enough for correct use.

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

All Samuelz® Marketing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?