support_response_list

Tool

support_response_list

List the responses of ONE survey, newest first — surveyId is required, because a page mixing two surveys would carry answers keyed by two different question sets.

List the responses of ONE survey, newest first — surveyId is required, because a page mixing two surveys would carry answers keyed by two different question sets. Filters: score range (scoreMin/scoreMax, inclusive — a response with no score matches neither bound), a creation window (from/to), completed, plus pagination

Behavior

HTTP: GET /support/responses

Arguments

Name	Type	Required	Description
to	string	—	Only responses created at or before this ISO-8601 timestamp
from	string	—	Only responses created at or after this ISO-8601 timestamp
limit	integer	—	Page size, 1..100 (default 25)
offset	integer	—	Number of responses to skip
scoreMax	integer	—	Only responses scored at or below this value (inclusive). A response with no score matches neither bound — not even at the bottom of the scale
scoreMin	integer	—	Only responses scored at or above this value (inclusive). A response with no score matches neither bound — not even at the bottom of the scale
surveyId	string	•	Required: responses are always read one survey at a time
completed	boolean	—	true: only responses that reached the end. false: only partial ones

Response

Field	Type	Always	Description
limit	integer	•	Page size that was applied
offset	integer	•	Offset that was applied
responses	array	•	The requested page of responses, newest first

Try it

List the responses of ONE survey, newest first — surveyId is required, because a page mixing two surveys would carry answers keyed by two different question sets.

When to use

Example

Ask your agent something like this:

List the responses of ONE survey, newest first — surveyId is required, because a page mixing two surveys would carry answers keyed by two different question sets.

The agent will invoke support_response_list with these arguments:

{
  "surveyId": "<surveyId>"
}