Skip to main content
Glama

Clipform

by io.github.Clipform

Create Clipform

clipform_create_form

Create a new Clipform (interactive video-style form). Returns a viewer URL and form ID. When connected via an authenticated MCP client (e.g. claude.ai), the form lands directly in the user's workspace. Anonymous sessions get a claim URL to transfer ownership later.

Node types (omit config to use defaults where shown):

  • choice: Single or multiple choice node with predefined options (supports options array). Config: choice ({enable_branching, show_answer_feedback, record_scores}), selection_mode ("single"|"multiple", default: "single"), allow_text_response (boolean, default: false), randomise_options (boolean, default: false), show_option_count (boolean, default: false), option_display ("list"|"letters", default: "list"). Defaults: {"selection_mode":"single","choice":{"enable_branching":false},"randomise_options":false,"show_option_count":false,"option_display":"list"}

  • open: Free-form text responses from users. Config: formats (array of {format, order}), max_recording_seconds (number, default: 120). Defaults: {"formats":[{"order":0,"format":"text"},{"order":1,"format":"audio"},{"order":2,"format":"video"}]}

  • details: Collect several fields on one screen - name, email, phone, address, date, and more. Config: title (string), fields (array of {id, type, label, order, required, is_custom}), description (string), consent_items (array of {id, name, label, order, type}), Available field IDs: first_name, last_name, email, phone. Defaults: {"fields":[{"id":"first_name","type":"first_name","label":"First Name","enabled":true,"required":true},{"id":"email","type":"email","label":"Email","enabled":true,"required":true}],"consent_items":[]}

  • button: Simple button for acknowledgment or navigation (supports options array). Config: button_text (string, default: "Continue"), button_style ("primary"|"secondary"|"outline", default: "primary")

  • redirect: Redirect users to an external URL. Config: url (string), auto_redirect (boolean, default: true). Defaults: {"url":"","auto_redirect":true}

  • file_download: Provide a file for respondents to download. Config: files (array of {file_name, display_name, file_path, file_size, mime_type}), button_text (string, default: "Continue"), description (string)

  • end_screen: Final screen shown when form is completed. Config: title (string, default: "Thank you!"), message (string, default: "Your response has been submitted."), show_score (boolean, default: false), icon ("tick"|"trophy"|"star"|"crown"|"party"|"none", default: "tick"), show_share_button (boolean, default: false), cta_type ("none"|"restart"|"external_link", default: "none"), cta_text (string, default: "Continue"), cta_url (string), score_ranges (array of {min, max, title, message}), scoring_results (array of {category, title, message, cta_url, cta_text}). Defaults: {"title":"Thank you!","message":"Your response has been submitted."}

All type definitions and config schemas are derived from @vid-master/config (node-types). Refer to the config descriptions above for the correct keys and shapes. AI-PROTECTED parameters have restrictions noted in their descriptions.

Example: A form that asks a question, collects contact info, then finishes: { title: "Quick Survey", nodes: [ { type: "open", prompt: "What's your biggest challenge?" }, { type: "details", prompt: "Leave your details", config: { fields: [{ id: "first_name", required: true }, { id: "email", required: true }] } }, { type: "end_screen", prompt: "Thanks for your response!" } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags for indexing (e.g. ['quiz', 'trivia', 'arsenal']). Include format, genre, and topics.
nodesYesOrdered list of nodes/steps for the form
titleYesForm title
contextYesDescribe the user's underlying goal in one sentence - not the tool you're calling.
font_familyNoAI-PROTECTED: Only set when the user explicitly requests a specific font.
primary_colorNoPrimary/brand color as 6-digit hex (e.g. '#FF5500'). Used for buttons and accents.
background_colorNoBackground color as 6-digit hex (e.g. '#1A1A2E').
show_step_counterNoShow step counter (e.g. '1/5'). Set true for quizzes.
disable_back_navigationNoPrevent going back. Set true for quizzes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNoPlan and auth context for this session
nodesYesCreated nodes in order - IDs for attach_node_media / update_node
form_idYesForm UUID - pass to follow-up tools
viewer_urlYesForm URL for respondents - a live public URL once authenticated/published, or a scoped preview-only link for an anonymous session
dashboard_urlNoBuilder URL (sign in to edit)

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true). The description adds substantial operational behavior: it returns a viewer URL and form ID, lands the form in the user's workspace for authenticated clients, and gives anonymous sessions a claim URL. It also documents node-level defaults and AI-PROTECTED restrictions, far exceeding what annotations alone convey.

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 long, but every section earns its place: core return behavior first, then node-type specifications, then a worked example. It is well-structured with bullet-like formatting and bold labels. A 5 would require even tighter phrasing; a 4 acknowledges it is dense yet justified for the complexity of configurable node types.

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?

Given the tool's complexity, the description covers all needed information: creation behavior, return values, authentication implications, every node type with defaults, a concrete example, and pointers to protected parameters. The presence of an output schema for return structure does not create gaps here; the description fully equips an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema description coverage is 100%, the schema's config parameter is an opaque generic object. The description compensates by enumerating each node type with its configuration keys, defaults, allowed values, and constraints (e.g., choice selection_mode, open max_recording_seconds, details field IDs). This is exactly the semantic depth an agent needs to construct valid node configs.

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?

The description opens with a specific verb and object ('Create a new Clipform'), identifies the resource type, and states the key return values ('viewer URL and form ID'). It clearly differentiates from siblings like clipform_update_form, clipform_delete_form, and clipform_import_form, so an agent can select this tool unambiguously.

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 clearly explains the context around creation, including the difference between authenticated MCP sessions and anonymous sessions, and provides an example. It does not explicitly name alternatives or state when not to use this tool, but the creation-specific wording and sibling names make the intended use obvious. This is clear context without explicit exclusions, matching a 4 rather than a 5.

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