QuestionPunk

Responses List

responses_list

Read-onlyIdempotent

List a survey's responses (sessions), oldest first, 35 per page, with optional filters. Use it to find a userSessionId for response_get_details. For a count use responses_get_counts; to read and analyze the answers themselves use responses_read, which returns answers as JSON in larger pages.

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>"
    },
    "name": "responses_list"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number
`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)
`urlParamKey`	No	A URL parameter the survey defines (e.g. case_ref, from the link ?case_ref=...). With urlParamValue, lists only responses whose link carried that value.
`responseType`	No	Real respondents or synthetic (AI) responses. Omit for both.
`urlParamValue`	No	The whole value of urlParamKey to match (case-insensitive, e.g. SYNTH-0001). Required with urlParamKey.
`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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral detail the annotations cannot: default sort order (oldest first) and a fixed page size of 35, both of which affect how an agent must paginate. It stops short of describing how to detect the last page or whether a total count is returned, leaving that to the output schema.

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?

Three tight sentences, front-loaded with what the tool returns, followed by the routing hint and the alternatives. Every sentence carries information an agent would otherwise have to infer.

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 an output schema present and 100% parameter documentation in the input schema, the description only needs to cover purpose, ordering/paging behavior and sibling routing — all of which it does. Minor omissions such as the default page value or whether the response indicates more pages exist are covered or inferable from the schemas.

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% and the ten parameters have detailed per-field descriptions (Unix ms formats, the urlParamKey/urlParamValue pairing, enum meanings). The description adds nothing parameter-level beyond the phrase 'with optional filters', so the schema is doing all the work — the baseline 3 applies.

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 a survey's responses (sessions)') plus its ordering and page size, so an agent knows exactly what it retrieves. It also distinguishes itself from responses_get_counts and responses_read by naming them explicitly.

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?

Gives an explicit primary use case (find a userSessionId for response_get_details) and routes two adjacent needs to named alternatives: responses_get_counts for totals and responses_read for answer payloads in larger pages. There is no ambiguity about when to pick this tool over its siblings.

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?