Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

List Responses Tool

list-responses-tool
Read-onlyIdempotent

List the AI responses collected for a project, newest first. Returns up to 50 per page; follow nextCursor to fetch additional pages. Optionally pass prompt_id to return only the responses for a single prompt, or source_url_id to return only the responses that cite a given source URL. Pass include to load parent chains (prompt, monitor, project, organization). Brand mentions and citations are not embedded; query /v1/brand-mentions and /v1/citations separately.

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_id": "<project_id>"
    },
    "name": "list-responses-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor. Omit on the first call; pass the `nextCursor` value from the previous response to fetch the next page.
includeNoOptional comma-separated related resources to include in the response. Whitelisted: `prompt`, `prompt.monitor`, `prompt.monitor.project`, `prompt.monitor.project.organization`, `monitor`, `monitor.project`, `monitor.project.organization`, `project`, `project.organization`.
prompt_idNoOptional filter. Only return responses for this prompt.
project_idYesThe numeric id of the project whose responses should be listed.
source_url_idNoOptional filter. Only return responses that cite this source URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, yet the description still adds genuine operational detail: page size capped at 50, newest-first ordering, and the important disclosure that brand mentions and citations are NOT embedded in results. Return object shape is left unspecified, but no output schema exists so that is a minor gap.

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-loaded with purpose and ordering, then pagination, then filters, then exclusions - a sensible information hierarchy with no filler. Minor redundancy exists between the filter sentences and the already-descriptive schema, which keeps it from a 5.

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 five-parameter read-only list tool with no output schema, the description covers ordering, page size, pagination traversal, filtering, relation loading, and what related data is deliberately excluded. An agent has everything needed to call it correctly and interpret the result boundaries.

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 3; the description earns above that by explaining the intent of `include` ('load parent chains (prompt, monitor, project, organization)') rather than just listing whitelisted values, and by framing `prompt_id`/`source_url_id` as narrowing filters.

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 the AI responses collected for a project') plus ordering ('newest first'), and explicitly scopes out brand mentions and citations so it is distinguishable from list-brand-mentions-tool and list-citations-tool.

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?

Gives clear conditional guidance for the two optional filters ('pass `prompt_id` to return only...'), explains when to use `include`, and routes the agent to /v1/brand-mentions and /v1/citations for related data. It stops short of comparing against sibling analytics tools, so there is no explicit when-not-to-use-this-tool statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pineprompt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources