Skip to main content
Glama

Visibility Genies

Get shared keywords

get_shared_keywords

The keywords several pages, folders or whole sites rank for in Google, highest search volume first, with each one's position and ranking page beside it: your page against competing pages, your own pages against each other (cannibalization), or your site against a competitor's. Estimated price: up to $0.05, one market data request for up to 100 keywords, billed by the rows returned. The same comparison and market saved within 12 hours is read free, in any order of the pages, and it opens free on the Shared Keywords page. 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>",
      "pages": "<pages>"
    },
    "name": "get_shared_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'all': keywords every page ranks for on the same results page. 'any': keywords any of them ranks for.all
pagesYes1 to 20 page addresses or folders to compare. A folder ends in /*, and a whole site is its domain with /*, such as 'example.com/*'. Two or more in all, with excludePages.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
excludePagesNoUp to 10 pages or folders whose keywords are left out, such as your own site to see what only the others share.
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.3/5.0
Behavior5/5

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

Far beyond the annotations, it discloses the price ceiling ($0.05 per 100-keyword request, billed by rows), free re-reads of the same comparison/market within 12 hours, the $2.00 agent spend limit behavior, that the hold is estimate-plus-margin and charged only for what was bought, and that over-limit calls are refused before purchase. These are the exact traits an agent needs to decide whether to call or ask the user first.

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 purpose is front-loaded and every paragraph carries substantive content, though the pricing sentences are dense and partly overlap (estimate, per-call maximum, and refusal are restated across three sentences). Slightly repetitive but not padded with filler.

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?

With an output schema present and full schema coverage, the description still covers the things structured fields don't: cost, caching, spend-limit enforcement, and the escalation path to the user. For a billed, open-world tool this is complete enough 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, and the description earns above it by explaining approvedMaxCostUsd as a post-refusal, user-approval-only parameter and by flagging the locationCode market caveat (Iceland/2352 having no difficulty, intent, or domain data). It still leaves pages, excludePages, and mode to the schema.

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 a specific resource and scope: keywords that several pages, folders, or whole sites rank for in Google, returned highest-search-volume-first with position and ranking page. That multi-page scope implicitly separates it from single-site keyword tools, but it never names a sibling (e.g. get_ranked_keywords) as the alternative, so the agent must infer the routing.

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 clear context for the three comparison scenarios (your page vs competitors, your own pages for cannibalization, your site vs a competitor) and states the exact procedure for a cost-refused call. It stops short of explicit when-not-to-use or sibling-alternative guidance, but the use cases are concrete rather than implied.

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