Skip to main content
Glama

list_ai_answers

Read-only

The actual AI answers behind a project's visibility numbers, newest first: which engine answered which tracked prompt, whether the brand was named and at what position, which competitors were named, how many sources the answer used, and a short excerpt. Filters: promptId, model, brandMentioned, days, source; paged with limit (default 20, max 50) and offset (nextOffset). get_ai_answer opens one answer with its full text, cited URLs and the engine's searches. Answer text is third-party content, named in untrustedContent. How the list relates to the metrics, and what the source-count flags mean, arrives in howToRead and note.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ai_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days (default 30, max 180).
limitNoAnswers per page (default 20, max 50).
modelNoOnly this engine/model id, e.g. "gpt-4o-search-preview".
marketNoOnly this market, exactly as listed in marketsInWindow (an answer's locale).
offsetNoAnswers to skip — nextOffset from the previous page.
sourceNoData source: "blended" (default — CrunchJunkie scans plus imported Peec data, an engine both track counted once with the CrunchJunkie scan winning), "native" (CrunchJunkie scans only) or "peec" (imported Peec data only).
clientIdNoClient id — uses the AI-Visibility project its Overview opens in the app (the newest).
promptIdNoOnly answers to this tracked prompt (id from list_prompts).
projectIdNoAI-Visibility project id.
brandMentionedNotrue = only answers that name the brand; false = only answers that don't.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / market
      Added value: +{
      +  "description": "Only this market, exactly as listed in marketsInWindow (an answer's locale).",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Changed2 schema fields changed
    • changedInput schema / properties / offset / description
      Previous value: -"Answers to skip — pass nextOffset from the previous page."New value: +"Answers to skip — nextOffset from the previous page."
    • changedInput schema / properties / source / description
      Previous value: -"Data source: \"blended\" (default — your scans plus imported Peec data, an engine both track counted once with your scan winning), \"native\" (your scans only) or \"peec\" (imported Peec data only)."New value: +"Data source: \"blended\" (default — CrunchJunkie scans plus imported Peec data, an engine both track counted once with the CrunchJunkie scan winning), \"native\" (CrunchJunkie scans only) or \"peec\" (imported Peec data only)."
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false, so safety is covered; the description adds meaningful behavior beyond them — ordering, page-size default and hard max, the `nextOffset` continuation pattern, and a security-relevant warning that answer text is third-party content surfaced in `untrustedContent`. It also flags that explanatory context arrives in `howToRead` and `note`, so the agent knows not to interpret raw counts alone.

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?

Purpose and ordering are front-loaded in the first clause, then filters, then pagination, then the sibling pointer, then warnings — a sensible priority order. The sentences are dense and multi-clause, but each clause carries information (field list, paging, untrusted content, howToRead) rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

PLACEHOLDER

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%, so the schema already documents every parameter including the market/source nuances. The description restates the filter names and the limit/offset defaults without adding syntax or format guidance beyond the schema, and it omits the market and clientId/projectId scoping parameters entirely. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Opens with a specific verb and resource — the actual AI answers behind a project's visibility numbers — plus ordering ('newest first') and an enumeration of the fields surfaced (engine, prompt, brand mention and position, competitors, source count, excerpt). It also distinguishes itself from the sibling get_ai_answer by scope, so an agent can pick between list and detail without reading either schema.

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?

Explicit routing to the alternative: 'get_ai_answer opens one answer with its full text, cited URLs and the engine's searches,' implying this tool is for browsing/summarizing. Filter list and pagination mechanics are stated, but there is no explicit when-not-to-use guidance (e.g. when to prefer get_ai_visibility_metrics for aggregates rather than raw answers).

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