Skip to main content
Glama

get_keyword_opportunities

Read-only

Where to start for a client, from its own data. (1) Striking distance — Search Console queries at an average position of 4–20 in the last 30 days (all countries), most impressions first, with the monthly searches already stored for the chosen country and language (a stored lookup, or a Google Ads figure the workspace looked up), and what one lookup of the missing figures would cost. (2) The plain searches AI engines ran for the client's tracked prompts, with runs of n answers and the window. Reads only; lookup_keyword_volumes fetches the missing figures, research_keywords researches a seed.

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": {
      "clientId": "<clientId>",
      "country": "<country>",
      "language": "<language>"
    },
    "name": "get_keyword_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows of each list (default 25).
countryYesISO 3166-1 alpha-2 country the volume is for.
clientIdYesClient id (from list_clients).
languageYesLanguage code, e.g. "en", "de".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, and the description merely reinforces this with 'Reads only.' It does add useful non-annotation context: the fixed 30-day window, all-countries scope for positions, most-impressions-first ordering, and that it reports the cost of a missing-figure lookup. It says nothing about how the two lists interact, result size behavior, or what happens when no data is stored.

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

Conciseness3/5

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

The numbered (1)/(2) structure is helpful, but the first item is a single run-on sentence with multiple nested parentheticals and em-dashes that is hard to parse on one read. Information density is high and little is pure padding, yet the same content would land better as short bullets.

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?

With no output schema, the description does the necessary work of enumerating both returned lists and their key fields (positions, impressions, stored volumes, runs of n answers, window). It also flags the cost of filling volume gaps. Minor gaps remain around pagination, empty-state behavior, and whether limit applies independently to each list.

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?

Schema coverage is 100%, so all four parameters are already documented, making 3 the baseline. The description adds modest meaning beyond the schema by explaining that country and language select which pre-stored monthly search figure is joined onto the striking-distance rows, and that limit governs 'rows of each list'. It gives no format guidance for country/language beyond what the schema already states.

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 names the resource concretely: it returns two kinds of opportunity data — striking-distance Search Console queries (positions 4–20, last 30 days) and the plain searches AI engines ran for tracked prompts. That is far more specific than the name alone, though the lead sentence ('Where to start for a client, from its own data') is abstract and only becomes clear once the numbered list is read.

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 routes the agent explicitly: use this for starting points, use lookup_keyword_volumes to fetch the missing volume figures, and research_keywords to research a seed. That is clear conditional routing to two siblings. It stops short of stating when not to use this tool (e.g. for clients without Search Console or tracked prompts).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources