Skip to main content
Glama

Visibility Genies

List saved results

list_saved_results
Read-only

Lists the answers this project's paid tool calls returned, newest first: when, which tool, what was asked, what it cost and the first sentence of its answer. Every answer a tool that buys data returns is saved, except those of run_rank_tracker and run_site_audit, whose work is saved with the tracker or audit. Read one again with read_saved_result instead of buying it again. Uses no credits.

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>"
    },
    "name": "list_saved_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoOnly the results of this tool, e.g. get_business_reviews.
limitNoResults per page (1-50). Defaults to 20.
offsetNoHow many of the newest results to skip. Defaults to 0.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
hasMoreYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond them: newest-first ordering, the returned field set, the exclusion of tracker/audit work, and the zero-credit cost. It stops short of describing pagination behavior or result volume, which matters for a list tool capped at 50 per page, so it lands mid-range against the lower bar set by annotations.

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

Conciseness5/5

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

Two sentences, front-loaded with what is listed, followed by exclusions and the cost-free re-read path. Every clause carries information: fields returned, ordering, exceptions, and the cheaper alternative.

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?

An output schema exists, so return values need no prose, and annotations carry the safety profile. For a read-only list tool with one required parameter, the description supplies everything an agent needs: scope, ordering, exclusions, cost, and the follow-up 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 coverage is 100%, so tool, limit, offset and projectId are already documented in the schema, including the enum and the pointer to list_projects. The description adds only the "newest first" framing, which implicitly gives offset its meaning as skipping newest results, but it adds no filter or pagination guidance beyond what the schema states.

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 ("Lists the answers this project's paid tool calls returned") and immediately scopes it with ordering, returned fields, and two named exclusions (run_rank_tracker, run_site_audit). The agent can distinguish it from read_saved_result and from the many get_saved_* siblings without opening any 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 the substitute action explicitly: "Read one again with read_saved_result instead of buying it again," and quantifies the tradeoff with "Uses no credits." It also carves out two tools whose output is not listed here, which prevents wrong expectations.

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