Skip to main content
Glama

Visibility Genies

Read a saved keyword gap

get_saved_keyword_gap
Read-only

Reads a keyword gap saved by Domain Overview's Content gap tab or get_keyword_gap for this domain, competitor and market, for free. It never buys: a gap that is not saved, or no longer current, is named with the price get_keyword_gap would pay for it.

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_saved_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.

Output Schema

NameRequiredDescriptionDefault
metaNo
savedNo
boughtNo
keywordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the call is free, 'never buys', and a miss or stale gap is reported with the price get_keyword_gap would pay rather than erroring — the key cost semantics an agent needs. It leaves 'no longer current' undefined (no staleness threshold), which keeps it from a 5.

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?

Two compact sentences, the identifying scope and the free/no-purchase constraint front-loaded, with no filler or redundancy.

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?

Five documented parameters plus an output schema mean the description need not explain return values or field formats. It supplies what structure cannot: the fact that the read is free and what happens on an unsaved or stale gap. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, with required projectId and competitor and defaults for domain, languageCode and locationCode all documented in the schema itself. The description only echoes the domain/competitor/market triple that identifies a gap, adding no format or default nuance beyond the schema. Baseline 3 applies.

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 opens with a specific verb and resource ('Reads a keyword gap') and names the exact provenance: saved by Domain Overview's Content gap tab or by get_keyword_gap. That distinguishes it from the sibling get_keyword_gap, which computes/buys a fresh gap, without opening either schema.

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?

Usage context is clear: this tool is for gaps already saved for 'this domain, competitor and market', and implicitly the alternative is get_keyword_gap, whose price is quoted when the gap is missing or stale. It stops short of an explicit imperative ('if not saved, call get_keyword_gap'), but the routing is reasonably inferable.

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