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'.

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.

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.8/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses additional behavioral traits: redaction of contact details, file uploads, audio/video answers, and payment details staying in the dashboard. This is valuable non‑obvious behavior not captured in the schema.

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 description is slightly long and contains a somewhat convoluted clause about redaction that repeats 'payment details'. However, it is front‑loaded with the core purpose and examples, and remains readable and focused.

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?

With an output schema present, no return‑value explanation is needed. The description covers purpose, usage, behavior, and relationship to siblings, making it fully self‑contained for an agent to decide when and how to call the tool.

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 descriptions cover all 7 parameters (100% coverage), so baseline is 3. The description adds marginal value by clarifying that responses contain text answers and a non‑PII payment summary, which indirectly reinforces parameter usage (e.g., query searches text answers).

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?

Clearly states it lists individual form responses with time filtering, and explicitly distinguishes from clipform_get_results (aggregates). Examples of questions it answers further clarify its purpose.

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?

Explicitly names the complementary sibling tool (clipform_get_results) and explains the difference (individual responses vs. aggregates). Provides concrete example use cases, making it obvious when to choose this tool.

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.