Skip to main content
Glama

List the stored AI search answers one by one

visibility_list_results
Read-onlyIdempotent

Lists the stored AI search answers for a project one row per prompt, engine and run, newest first, with the same filters as visibility_get_summary. Each row carries the answer id, date, run id, engine, topic, prompt, branded or non-branded, whether the brand was mentioned and cited, its rank, the page cited, the sentiment, narrative and feature parity verdicts, and the competitors mentioned and cited. fields full adds the scorer reasons, the sources the engine listed, every brand named with its rank and sentiment, and a short excerpt of the answer. Paged: default 50 rows, at most 200; pass the nextCursor back to get the next page. Use it to build tables, spreadsheets and custom analyses, or to find the answers behind a number from visibility_get_summary; prefer narrow filters and several pages over one huge pull. Call visibility_get_answer with an answer id for the full text of one answer. Reads stored results only, never runs new checks. Takes a few seconds per page.

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": {
      "project": "<project>"
    },
    "name": "visibility_list_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day of the window as YYYY-MM-DD. Default today.
fromNoFirst day of the window as YYYY-MM-DD. Default: lookbackDays before to.
sortNoOrder by date. Default newest.
citedNotrue: only answers that cite a page of the brand. false: only answers that do not.
pagesNoOnly prompts whose answers cited one of these pages, then every engine for those prompts. Takes page URLs or bare domains such as "example.com", the brand's own or any other site, as returned in the citations section.
cursorNoThe nextCursor from the previous page, with the same filters and sort.
fieldsNocompact (default) or full. full adds reasons, sources, brands named and an excerpt, about three times the size.
topicsNoOnly these topics, by the exact names from visibility_list_tracked. "Uncategorized" selects prompts with no topic.
enginesNoOnly these AI engines, by name from visibility_list_tracked, such as "ChatGPT" or "Perplexity". A plain name also matches its local-fetch variant.
projectYesThe Hi, Moose project, by its name as shown by list_projects. The projectId is also accepted.
promptsNoOnly these prompts, by exact text or promptId from visibility_list_tracked.
pageSizeNoRows per page. Default 50.
mentionedNotrue: only answers that mention the brand. false: only answers that do not.
narrativeNoOnly answers with this narrative verdict against the Brand Truth Profile: aligned, partial or drifted.
sentimentNoOnly answers where the brand was mentioned with this sentiment.
competitorNoOnly answers that mention this competitor, by name from visibility_list_tracked.
promptTypeNoOnly branded prompts (the prompt names the brand, an alias or an owned domain) or only non-branded prompts.
lookbackDaysNoWindow length in days when from is not given. Default 30.
featureParityNoOnly answers with this feature parity verdict: accurate, needs-review, inaccurate or not-applicable.

Output Schema

NameRequiredDescriptionDefault
rowsNo
sortNo
errorNo
jobIdNo
rangeNo
totalNoRows matching the filters in the window, across all pages.
fieldsNo
statusNodone, failed, pending or running.
filtersNoThe filters that were applied, after validation.
headlineNoOne sentence with the window, sample size and the main numbers.
pageSizeNo
progressNo
returnedNo
createdAtNo
dataNoticeNo
nextCursorNoPass back as cursor for the next page. null on the last page.
projectNameNo
schemaVersionNoVersion of this result shape. Fields are only added within a version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pages / description
      Previous value: -"Only prompts whose answers cited one of these page URLs, then every engine for those prompts, which is how the Page filter works in Hi, Moose."New value: +"Only prompts whose answers cited one of these pages, then every engine for those prompts. Takes page URLs or bare domains such as \"example.com\", the brand's own or any other site, as returned in the citations section."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive; the description reinforces and extends this with "Reads stored results only, never runs new checks" plus a latency note ("a few seconds per page") and a payload-size warning for fields=full ("about three times the size"). What it does not cover is what happens when a cursor expires or filters change mid-pagination, which the schema only hints at.

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?

The paragraph is front-loaded with the resource and row shape, then output columns, then paging, then usage guidance, with essentially no filler sentences. It is dense for a 19-parameter tool, though the long column enumeration could have been trimmed since an output schema exists.

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?

For a 19-parameter, paged read tool, the description covers grain, ordering, page limits, cursor reuse, the compact/full tradeoff, latency, and sibling handoff. With an output schema present, the column list is a bonus rather than a required return-value spec, so nothing an agent needs is missing.

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 baseline is 3; the description still adds real meaning by explaining paging mechanics ("default 50 rows, at most 200; pass the nextCursor back to get the next page") and the concrete delta of fields=full ("adds the scorer reasons, the sources the engine listed, every brand named with its rank and sentiment, and a short excerpt"). It stops short of describing how filters interact (e.g. whether the pages filter expands to all engines), which is left to the schema.

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?

The description opens with a specific verb and resource ("Lists the stored AI search answers for a project") and immediately defines the row grain ("one row per prompt, engine and run") and ordering ("newest first"). This clearly distinguishes it from visibility_get_summary (aggregate numbers) and visibility_get_answer (single full answer).

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?

It states concrete use cases ("build tables, spreadsheets and custom analyses, or to find the answers behind a number from visibility_get_summary"), prescribes a strategy ("prefer narrow filters and several pages over one huge pull"), and routes to the sibling for the other need ("Call visibility_get_answer with an answer id for the full text of one answer"). It also anchors filtering behavior to visibility_get_summary's filter set.

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