Skip to main content
Glama

List visibility runs

list-visibility-runs
Read-only

List visibility runs for a domain, newest first, as an array with id, status, completed_at and engines; engine_shortfall, when present, names engines that answered fewer prompts than expected (dropped of expected). With one_per_day, list only completed runs, one per day (that day's latest, the run the Visibility page shows), each with its day. Run ids feed get-visibility-summary, get-visibility-score and compare-visibility-runs; the last two also take days. one_per_day reads at most 500 of the newest runs, so it may return fewer than limit days.

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": {
      "domain_id": "<domain_id>"
    },
    "name": "list-visibility-runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10
domain_idYesDomain ID from list-domains
time_zoneNoIANA time zone that decides which day a run belongs to. Defaults to UTC.
one_per_dayNoCompleted runs only, one per day (the latest run of each day).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
    • changedInput schema / properties / limit / description
      Previous value: -"Max results"New value: +"Max results, default 10"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_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.5/5.0
Behavior5/5

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

Annotations already declare a safe read, and the description layers on substantive behavior: return shape, engine_shortfall semantics ("answered fewer prompts than expected (dropped of expected)"), the one_per_day filtering/dedup rule, and the 500-run scan cap that can yield fewer than `limit` days. That cap caveat is exactly the kind of non-obvious trait annotations can't convey.

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?

Front-loads the core purpose and return shape, then layers the one_per_day mode and the downstream consumers. Dense but nearly every clause carries information; the engine_shortfall parenthetical is slightly cryptic but functional.

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 carries the return-value burden and does so reasonably (id, status, completed_at, engines, optional engine_shortfall, `day` under one_per_day). It stops short of describing possible `status` values or the engines entry shape, leaving minor gaps for a list tool.

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 met, but the description adds real meaning beyond it: one_per_day means completed-only, latest-per-day, with a `day` field; the 500-run cap interacts with `limit`. time_zone's role in day assignment is implied ("which day a run belongs to") but not spelled out.

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 ("List visibility runs for a domain") plus ordering ("newest first") and the returned fields (id, status, completed_at, engines). It is clearly distinguishable from siblings like get-visibility-summary or compare-visibility-runs, whose ids it supplies.

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?

Explicitly routes the agent downstream ("Run ids feed get-visibility-summary, get-visibility-score and compare-visibility-runs") and explains the one_per_day mode as the run the Visibility page shows. It doesn't state when *not* to use it, but the mode selection and consumer relationships are clear.

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