Skip to main content
Glama

Clipform

by io.github.Clipform

Get Clipform Results

clipform_get_results
Read-onlyIdempotent

View response counts, choice/action answer breakdowns, and recent open-text answers for a form. Contact, file, draw, camera, and payment answers are counts only - use the dashboard for per-response detail.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
nodesYesNodes in form order. Contact/file/draw/camera/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

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context: the tool returns counts only for certain answer types and only recent open-text answers, which is important for setting agent expectations beyond 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two focused sentences with no filler. The main result types are front-loaded, and the counts-only limitation is stated immediately after, making the definition easy to scan and follow.

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?

Given the presence of a full input schema, an output schema, and comprehensive read-only annotations, the description covers the essential behavioral caveats. The only notable gap is not steering the agent toward a sibling tool for per-response detail, but the dashboard reference mitigates this.

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 the parameters are fully documented in the schema. The description does not add parameter-specific semantics beyond the general phrase 'for a form', which is already implied by the schema.

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?

The description names a specific verb ('View') and precise resources: response counts, choice/action breakdowns, and recent open-text answers. It is clear about the tool's scope, though it does not explicitly differentiate itself from the similarly named sibling 'clipform_get_responses'.

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?

The description gives clear context for when this tool is useful: when aggregate counts and breakdowns are needed. It also provides an important limitation by noting that contact/file/draw/camera/payment answers are counts only and directing to the dashboard for per-response detail, though it does not name an alternative MCP tool.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Most form/node CRUD tools are clearly distinct, but the render/generate trio (generate_video, render_video_template, render_composition) and get_responses vs get_results can be confused by name alone. The descriptions include strong disambiguation guidance, so the overlap is manageable but still present.

Naming Consistency4/5

The vast majority of tools follow a consistent clipform_verb_noun snake_case pattern, with create/get/update/delete/list used predictably. Minor deviations include get_more_tools lacking the clipform_ prefix and whoami not matching the verb_noun convention.

Tool Count2/5

At 34 tools, this is above the range where a toolset feels well-scoped, and several entries are auxiliary or internal (whoami, log_generation, get_more_tools, search_news). The domain is broad, but the surface could be consolidated without losing core capabilities.

Completeness4/5

The set covers form and node lifecycle, media upload/attachment, logic wiring, publishing, responses/results, and content generation (TTS, video, music, stock media). Minor gaps remain, such as no conditional branching in set_logic and no general media-library listing tool.

Resources