QuestionPunk

Report Load More Answers

report_load_more_answers

Read-onlyIdempotent

Page through one question's open-text answers as the report shows them, starting at page 1. To read many answers at once or several questions together, responses_read with questionIds is usually better. Accepts the same filters as report_get.

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": {
      "surveyId": "<surveyId>",
      "surveyItemId": "<surveyItemId>"
    },
    "name": "report_load_more_answers"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (starts at 1)
`status`	No	completed, abandoned (left before the end) or in_progress. Omit for all.
`dateEnd`	No	Only responses started at/before this time, as Unix milliseconds (13 digits)
`surveyId`	Yes	Survey ID (from survey_list)
`dateStart`	No	Only responses started at/after this time, as Unix milliseconds (13 digits; 2025-01-01T00:00Z is 1735689600000)
`responseType`	No	Real respondents or synthetic (AI) responses. Omit for both.
`surveyItemId`	Yes	Open-text question ID (from survey_get)
`suspiciousLevel`	No	Fraud-check filter. 'clean' excludes suspicious responses; 'flagged' is high + medium.
`surveyRevisionId`	No	Only responses collected on this published revision

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: results mirror the report's presentation order, paging begins at page 1, and filtering behaves like report_get. It does not disclose page size or what happens past the final page, which keeps it from a 5.

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 the core action and followed immediately by the routing alternative. Every clause carries information; there is no restatement of the title or filler.

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?

With nine parameters, full schema descriptions, an output schema and read-only annotations, the description only needs to add routing and paging semantics, which it does. The remaining gap is pagination mechanics (page size, termination), which an agent paging through results would want.

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 enums on three filters, so the schema carries the parameter burden and this is the baseline case. The description only adds the cross-reference that filters match report_get and that page 1 is the starting point, which is a marginal but real addition over 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 states a specific verb and resource ('Page through one question's open-text answers') plus scope ('as the report shows them, starting at page 1'). It explicitly contrasts with the sibling responses_read, so an agent can choose between them without opening 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 Guidelines5/5

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

It names the alternative tool and the condition that selects it: use responses_read with questionIds when reading many answers at once or several questions together. It also notes the filter set matches report_get, giving the agent a mental model for arguments.

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

All QuestionPunk tools Inspect

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

Need Help?