Skip to main content
Glama

Visibility Genies

Get the keyword gap

get_keyword_gap

Finds content gaps: the keywords a competitor ranks for in Google and your domain does not, highest search volume first, each with its search volume, difficulty and the competitor's position and page. Both sides are whole domains, subdomains included. One competitor a call; compare several with one call each. Estimated price: ~$0.05, one market data request for the top 100 keywords. The same gap and market saved within 12 hours is read free, and it opens free on Domain Overview's Content gap tab; get_saved_keyword_gap reads it without buying. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>",
      "competitor": "<competitor>"
    },
    "name": "get_keyword_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoYour domain. Defaults to the project's own.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
competitorYesThe competitor's domain, such as 'example.org'.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoMarket location code, for example 2840 for the United States. When left out, the project's default market is used (shown by list_projects and changed in project settings). A few countries, Iceland (2352) among them, only have Google Ads data: search volume, CPC and trends are available there, but keyword difficulty, search intent and domain analytics are not.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
savedNo
boughtNo
keywordsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description goes far beyond by disclosing price (~$0.05, one market data request for top 100), the 12-hour free-cache window, the workspace agent spend limit ($2.00 default), the hold-and-charge-at-most-estimate behavior, and the pre-purchase refusal with estimate and maximum. That is exactly the cost/side-effect context an agent needs before invoking.

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?

Front-loaded with the core gap definition and ordering, then cost and approval mechanics. It is dense and slightly long in the spend-limit sentences, but nearly every clause carries decision-relevant information an agent would otherwise have to guess.

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?

A paid, open-world tool with an output schema and 6 parameters; the description covers cost, caching, spend-limit refusal, retry semantics, and domain scoping. Return values are handled by the output schema, so nothing material is missing for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning on top — both sides are whole domains including subdomains, one competitor per call, and the approvedMaxCostUsd retry protocol after a refusal. It does not elaborate domain/languageCode/locationCode behavior beyond the schema, keeping it short of a 5.

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?

States a precise verb and resource — keywords a competitor ranks for in Google that your domain does not — plus ordering (highest search volume first) and returned fields (volume, difficulty, competitor position and page). It also differentiates from the sibling get_saved_keyword_gap by explaining that sibling reads an already-computed gap.

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

Usage Guidelines5/5

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

Explicitly sets the call granularity (one competitor per call; compare several with one call each), names the free alternative path (get_saved_keyword_gap, or the Domain Overview Content gap tab), and describes the escalation path when a call is refused for exceeding the spend limit. When-to-use and when-not-to-buy are both covered.

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