Skip to main content
Glama

Get visibility summary

get-visibility-summary
Read-only

Get the stored visibility summary of one run as a single object with scores, coverage, engine breakdown and competitor comparison. get-visibility-score scores a narrower scope. The run_id comes from list-visibility-runs. geo_visibility_score and competitor_scores are the NON-BRANDED score (prompts naming a brand, ours or a competitor's, are excluded); the *_branded fields hold the score for prompts naming only us, and the *_competitor_branded fields hold the score for prompts naming a competitor, including ones that also name us. Both pairs are null when the run had none of that type. When competitor_branded_prompt_count is null the run predates the split: geo_visibility_score_branded, competitor_scores_branded, branded_prompt_count and each engine_scores entry's geo_branded / competitor_scores_branded are then null too, because the stored values mixed both brand types. An engine_scores entry whose geo is null answered only brand-type prompts: it has no non-branded data (not a score of 0), only its brand-type fields. total_answers, answers_with_presence, coverage and average_answer_score are non-branded too: they count only the prompts behind geo_visibility_score, not every prompt in the run. By default each competitor list holds the 10 highest-scoring brands plus the tracked brand, competitors_omitted counts the rest, and engine_scores entries carry scores without per-engine competitor lists; detail "full" returns every list.

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": {
      "run_id": "<run_id>"
    },
    "name": "get-visibility-summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNocompact (default) trims competitor lists; full returns every competitor list, including per engine, and can be very large.compact
run_idYesRun ID from list-visibility-runs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / run_id / description
      Previous value: -"Visibility run ID"New value: +"Run ID from list-visibility-runs"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / run_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds substantial context beyond that: branded vs non-branded scoring semantics, null propagation rules for older runs, default competitor-list trimming, and the effect of detail='full'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description then becomes a dense single block of field-level semantics. Much of it is necessary for interpreting nulls and branded/non-branded fields, yet it could be structured more clearly and the important detail='full' note is buried at the end.

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?

With no output schema, the description must explain return values, and it does cover key fields, null conditions, and default trimming behavior. It still leaves some terms (e.g., 'coverage') and the full response shape less precisely defined, but it is largely complete for a read-only summary tool.

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%, and the schema already documents both run_id and detail, including the compact/full enum. The description repeats the run_id source and detail behavior but does not add new syntax or format guidance for the parameters; its extra detail is about output fields, not parameters.

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 ('Get the stored visibility summary of one run') and immediately names the return composition. It explicitly distinguishes itself from get-visibility-score by noting that sibling scores a narrower scope, and points to list-visibility-runs for the run_id.

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?

Names get-visibility-score as an alternative with a narrower scope and identifies list-visibility-runs as the source for run_id. However, it does not give explicit when-to-use conditions (e.g., 'use this when you need engine breakdown or competitor comparison') or mention compare-visibility-runs.

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