Skip to main content
Glama
Sign In

Clipform

by io.github.Clipform
OverviewDiscussionsAdmin

Get Clipform Results

clipform_get_results
Read-onlyIdempotent

View response counts, choice/action answer breakdowns, and recent open-text answers for a form. Answers to booking, contact details, file upload, drawing, camera, and payment nodes are counts only - use the dashboard for per-response detail. Needs a signed-in Clipform account (an anonymous session is asked to sign in).

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence - not the tool you're calling.
form_idYesThe form UUID (returned by clipform_create_form, not the short share_id from the URL)

Output Schema

NameRequiredDescriptionDefault
nodesYesNodes in form order. The booking, contact details, file upload, drawing, camera, and payment nodes carry only total_responses/total_views - no per-response detail.
results_urlNoDashboard Responses tab for this form. Not present for an anonymous caller.
total_responsesYesTotal unique respondents to the form

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / nodes / description
      Previous value: -"Nodes in form order. Contact/file/draw/camera/payment nodes carry only total_responses/total_views - no per-response detail."New value: +"Nodes in form order. The booking, contact details, file upload, drawing, camera, and payment nodes carry only total_responses/total_views - no per-response detail."
    • changedOutput schema / properties / nodes / items / properties / options / description
      Previous value: -"Answer breakdown - choice and action-category (booking/file_download/shopping) nodes only"New value: +"Answer breakdown - choice and action-category (file_download/shopping) nodes only"
  2. Changed1 schema field changed
    • addedOutput schema / properties / nodes / items / properties / selection_mode
      Added value: +{
+  "description": "Choice questions only. `multiple` = people could pick several options, so option counts add up past total_responses and the option percentages can sum past 100.",
+  "enum": [
+    "single",
+    "multiple"
+  ],
+  "type": "string"
+}
  3. Changed4 schema fields changed
    • 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"
+]
    • addedOutput schema / properties / results_url
      Added value: +{
+  "description": "Dashboard Responses tab for this form. Not present for an anonymous caller.",
+  "type": "string"
+}
  4. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world. The description adds genuinely new behavioral context: an authenticated Clipform account is required and anonymous sessions will be prompted to sign in. It also discloses a real data limitation (booking, contact, file upload, drawing, camera, payment nodes return counts only), which prevents the agent from promising per-response detail.

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?

Three sentences, each carrying a distinct payload: what you get, what you don't get, and what access is needed. Front-loaded with the returned content. Slightly dense but no 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 an output schema present, the description doesn't need to explain return shapes, and it correctly focuses on the auth requirement and the node-type data limitations. The one missing piece for a tool in a 29-sibling server is routing guidance versus clipform_get_responses.

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 both parameters (form_id, context) are documented there, including the warning that form_id is the UUID not the share_id. The description adds nothing about parameters beyond what the schema already says, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('View response counts, choice/action answer breakdowns, and recent open-text answers for a form'), so an agent knows exactly what data comes back. It fails to distinguish itself from the sibling clipform_get_responses, which by name alone looks like it does the same thing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It does name one alternative ('use the dashboard for per-response detail'), which is useful routing for detailed exports. But the sibling clipform_get_responses is never mentioned, so the agent has no guidance on when to pick one over the other.

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

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