Skip to main content
Glama

Visibility Genies

Read a saved domain comparison

get_saved_domain_comparison
Read-only

Reads a comparison of 2 to 5 domains saved by the Compare Domains page or compare_domains, however old, for free. It never buys: what is missing or out of date is named with the price compare_domains 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>",
      "domains": "<domains>"
    },
    "name": "get_saved_domain_comparison"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
metaNo
rowsNo
savedNo
domainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the description correctly spends its words on cost semantics ('for free', 'never buys') and staleness behavior (missing or out-of-date items are named with the price that would be incurred). That is real added context for an agent deciding whether to spend money. The gap is the failure case: no mention of what returns when no matching saved comparison is found.

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?

Two tight sentences, front-loaded with what the tool returns and the free/no-purchase guarantee. The colon construction in the second sentence is slightly compressed but every clause carries information; nothing is filler.

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?

An output schema exists, so return-shape explanation is unnecessary, and the readOnly annotations cover the safety profile. Combined with the cost and staleness notes, an agent has nearly everything needed. The only omission that matters is the no-saved-comparison case.

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%, so parameters (domains, projectId, languageCode, locationCode) are already fully documented including the 2–5 domain limit. The description only restates the domain count and adds nothing about how these parameters resolve against a saved comparison (e.g. whether domain order or language/location must match the original save). Baseline 3 is appropriate.

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 ('Reads a comparison of 2 to 5 domains'), names the provenance ('saved by the Compare Domains page or compare_domains'), and carves out the key distinction from the sibling that would perform a live purchase ('It never buys'). An agent can distinguish this from compare_domains 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?

Clearly frames the use case: fetch an already-saved comparison regardless of age, at no cost, with stale/missing pieces surfaced along with what compare_domains would charge. This implicitly routes fresh-data needs to compare_domains, though it never says outright 'use X when you need current data' nor states what happens if no saved comparison exists.

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