Clipform

List form responses

clipform_get_responses

Read-onlyIdempotent

List a Clipform form's individual responses (submissions) with time filtering - complements clipform_get_results (aggregates). Answers questions like 'what came in during the last 24 hours', 'what's the longest answer', 'what did people say'. Text answers plus a non-PII payment summary (amount and status); contact details, file uploads, and audio/video answers are redacted to placeholders and the customer's payment details stay in the dashboard (the responses URL from clipform_get_form). Responses are sorted newest first unless sort: 'oldest'. Needs a signed-in Clipform account (an anonymous session is asked to sign in).

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Order by submission time. Default: newest
`limit`	No	Max responses to return (default 20, max 50)
`query`	No	Only responses whose text answers contain this string (case-insensitive)
`since`	No	Only responses submitted at or after this ISO 8601 time (e.g. '2026-08-29T00:00:00Z')
`until`	No	Only responses submitted at or before this ISO 8601 time
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.
`form_id`	Yes	Form UUID (from clipform_list_forms / clipform_create_form)

Output Schema

TableJSON Schema

Name	Required	Description
`returned`	Yes	Responses in this result
`responses`	Yes	Matching responses, filtered/sorted/capped per the inputs
`total_matching`	Yes	Responses matching the filters (before the limit cap)
`locked_over_plan_limit`	Yes	Matching responses hidden by the plan's response limit

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

addedInput schema / properties / since / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

addedInput schema / properties / until / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

Changed3 schema fields changedAug 31, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence - not the tool you're calling.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "form_id"
-]New value: +[
+  "form_id",
+  "context"
+]

AddedAug 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial undisclosed behavior: contact details, file uploads and audio/video answers are redacted to placeholders, a non-PII payment summary is returned, full payment details remain in the dashboard via the URL from clipform_get_form, and a signed-in Clipform account is required. That is exactly the kind of auth, privacy and result-shaping context annotations cannot express.

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?

The scoping distinction from clipform_get_results is front-loaded and each sentence carries information (redaction, auth, ordering). It is a dense single paragraph with mild redundancy in the illustrative questions ('what's the longest answer', 'what did people say'), but nothing is wasted enough to warrant cutting.

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 7-parameter, read-only list tool with an output schema, the description covers everything the agent still needs: what is filtered, what is redacted, what the ordering default is, and the authentication prerequisite. Return-value shape is correctly left to the output schema.

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 every parameter (sort, limit, query, since, until, form_id, context) is already documented in the schema. The description restates the sort default ('newest first unless sort: oldest') but adds no syntax, format or constraint detail beyond what the schema provides, so 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 Clipform form's individual responses (submissions)') and immediately distinguishes itself from the closest sibling by noting it 'complements clipform_get_results (aggregates)'. An agent can tell which of the two listing tools to pick 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 Guidelines4/5

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

Explicitly contrasts this tool with clipform_get_results (aggregates), so the alternative is named and the split is implied, and it supplies concrete scenario questions ('what came in during the last 24 hours', 'what's the longest answer'). It stops short of an explicit when-not rule (e.g. 'do not use this for totals or charts'), so it is clear context rather than a full routing decision.

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

All Clipform 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.