Skip to main content
Glama

Visibility Genies

List saved prompt answers

list_saved_prompt_answers
Read-only

Lists every answer Prompt Explorer bought for this project, a run at a time, newest first: the prompt, how it was asked, and each model's or app's answer with its sources. Runs of tracked prompts are listed too, marked as Prompt Tracking samples (source: tracking). Answers stay saved for good, so what a model said months ago is read here. 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_prompt_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRuns per page (1-20). A run is one prompt asked of several models at once. Defaults to 10.
offsetNoHow many of the newest runs 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
runsYes
hasMoreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the bar is lower. The description still adds real behavior beyond them: results are ordered newest-first, paginated by run, tracked prompts are included but flagged as 'Prompt Tracking samples (source: tracking)', and the call consumes no credits.

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?

Three tight sentences, front-loaded with the scope and contents before the tracking and permanence notes. Minor marketing flavor ('bought', 'stay saved for good') but every sentence carries information the agent can act on.

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-value structure need not be explained, and all three params are fully documented in the schema. What remains is covered: ordering, paging unit, tracking-run flagging, and credit cost. Only the explicit list-vs-get routing to the sibling is missing.

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%, with limit and offset fully documented including the 'run' concept and defaults, so the baseline is 3. The description reinforces the run-as-page unit but adds no syntax, format, or constraint detail beyond what the schema already supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists every answer Prompt Explorer bought for this project') and enumerates the payload contents (prompt, how it was asked, each model's answer with sources). It implicitly contrasts with the sibling get_saved_prompt_answers by emphasizing enumeration 'a run at a time, newest first', but never explicitly says how it differs from that single-record getter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Useful context is present ('Answers stay saved for good, so what a model said months ago is read here', 'Uses no credits'), which implies this is the historical-retrieval entry point. However, there is no explicit when-to-use or when-not-to-use statement, and no mention of when to prefer get_saved_prompt_answers over this listing.

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