Skip to main content
Glama

Visibility Genies

Compare domains

compare_domains

Puts 2 to 5 domains side by side in one market: organic traffic and keywords (each domain's Domain Overview totals), paid search traffic and keywords, and each domain's ranking changes (keywords new, up, down and lost in the last check). Estimated price: up to $0.15 for 5 domains, up to $0.08 for 2: one request for the traffic of all of them and one for each domain's totals. Totals saved within 12 hours, here, on Domain Overview or by get_domain_overview, are read free, and so is a comparison saved within 12 hours. It opens free on the Compare Domains page; get_saved_domain_comparison 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>",
      "domains": "<domains>"
    },
    "name": "compare_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes2 to 5 domains to compare, e.g. ['example.com', 'example.org'], usually the project's own first.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
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
rowsNo
savedNo
domainsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses concrete pricing tiers, the billing model (one traffic request for all domains plus one per domain), the 12-hour cache that makes totals free, and the spend-limit mechanics (holds estimate plus margin, charged only what it bought, refused before purchase if the maximum exceeds the limit). What it omits is latency/return shape, but the output schema covers the latter. The readOnlyHint=false is consistent with a call that spends money, so there is no contradiction.

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?

Purpose and cost are front-loaded in the first sentences, and every clause carries operational information (price, caching, spend limit, refusal recovery). It is dense to the point of being a single long paragraph, and the cost figures and free-cache rules are restated in slightly different forms, but little is genuinely wasted.

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?

Return values need not be explained because an output schema exists, and the paid-call workflow, cost bounds, and failure recovery are all covered. A small gap remains around what happens to partially cached results (whether a mix of cached and fresh domains is prorated), but for a paid read tool this is close to complete.

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 baseline is 3; the description adds real meaning on top by tying the domains parameter's 2-to-5 bound to cost scaling ($0.15 at 5, $0.08 at 2) and by spelling out that approvedMaxCostUsd must reflect an amount the user actually approved after seeing an estimate. It does not add anything for languageCode/locationCode, but the schema already handles those.

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 specific verb and resource ("Puts 2 to 5 domains side by side in one market") and enumerates exactly what is compared: organic traffic/keywords, paid search traffic/keywords, and ranking changes (new, up, down, lost). It also names the sibling that reads the result without buying (get_saved_domain_comparison), so an agent can separate the two without opening a schema.

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?

Gives explicit routing: use this to buy a fresh comparison; use get_saved_domain_comparison to read one that already exists, and note that a comparison saved within 12 hours is free here too. It also prescribes the escalation path when a call is refused for exceeding the workspace spend limit — ask the user, then re-call with approvedMaxCostUsd — which is exactly the when/how guidance an agent needs.

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