Skip to main content
Glama

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, document, require_scroll_to_accept}), 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."), 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). 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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / nodes / items / properties / options / items / properties / score / description
      Previous value: -"Score value for this option (for scored quizzes). Use 1 for correct, 0 for wrong. Scored options automatically enable correct-answer marking (record_scores) on the node."New value: +"Score value for this option (for scored quizzes). Use 1 for correct, 0 for wrong. Scored options automatically enable correct-answer marking (record_scores) and correct/incorrect answer feedback on the node; set config.choice.show_answer_feedback: false to hide the feedback."
  2. Changed2 schema fields changed
    • addedInput schema / properties / nodes / items / properties / options / items / properties / is_correct
      Added value: +{
      +  "description": "Mark this as the correct answer for a quiz (maps to score 1; other options score 0). Use this OR score, not both.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / nodes / items / properties / options / items / properties / scores
      Removed value: -{
      -  "additionalProperties": {
      -    "type": "number"
      -  },
      -  "description": "Planned feature - category-based scores keyed by category name. Not yet editable in the dashboard.",
      -  "type": "object"
      -}
  3. Changed3 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: -[
      -  "title",
      -  "nodes"
      -]New value: +[
      +  "title",
      +  "nodes",
      +  "context"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / properties / viewer_url / description
      Previous value: -"Live form URL for respondents"New value: +"Form URL for respondents - a live public URL once authenticated/published, or a scoped preview-only link for an anonymous session"
  5. Changed1 schema field changed
    • changedInput schema / properties / nodes / items / properties / type / enum
      Previous value: -[
      -  "choice",
      -  "open",
      -  "details",
      -  "draw",
      -  "button",
      -  "redirect",
      -  "file_download",
      -  "end_screen"
      -]New value: +[
      +  "choice",
      +  "open",
      +  "details",
      +  "button",
      +  "redirect",
      +  "file_download",
      +  "end_screen"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / nodes / items / properties / type / enum
      Previous value: -[
      -  "choice",
      -  "open",
      -  "contact",
      -  "draw",
      -  "button",
      -  "redirect",
      -  "end_screen"
      -]New value: +[
      +  "choice",
      +  "open",
      +  "details",
      +  "draw",
      +  "button",
      +  "redirect",
      +  "file_download",
      +  "end_screen"
      +]
    • changedOutput schema / properties / nodes / description
      Previous value: -"Created nodes in order - IDs for upload_node_media / update_node"New value: +"Created nodes in order - IDs for attach_node_media / update_node"
  7. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses substantial behavioral details: authenticated clients place the form in the user's workspace, anonymous sessions receive a claim URL, and the tool returns both a viewer URL and form ID. It also documents per-node defaults, config shapes, and AI-PROTECTED restrictions, which gives the agent realistic expectations for the mutation.

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 well-structured: the core purpose and ownership behavior are front-loaded, followed by node-type details and an example. The final provenance note about @vid-master/config is slightly redundant but does not seriously detract from usability.

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 creation tool with nine parameters, nested node configs, and seven node types, the description is remarkably complete. It covers return values, authentication-dependent behavior, defaults, config schemas, constraints, and provides an example, while the output schema fills in the remaining return-value details.

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?

Although the input schema already covers all parameters, the description adds significant value by documenting the seven node types, their config keys, default values, and constraints like allowed option counts. The worked example also makes the relationship among title, nodes, and config much clearer than the schema alone.

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 clearly identifies the operation as creating a new Clipform, defines it as an interactive video-style form, and states the key return values (viewer URL and form ID). This differentiates it from siblings like clipform_update_form and clipform_list_forms without ambiguity.

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 using the tool: creating a new form, with ownership/workspace behavior explained for both authenticated and anonymous MCP sessions. It does not explicitly name alternatives like clipform_update_form or clipform_import_form, but the creation context is unmistakable and the example reinforces the intended workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: form CRUD, node management, media upload/attach, rendering, search, and guidance retrieval are all separable. The main overlap is among the three render tools (clipform_generate_video, clipform_render_video_template, clipform_render_composition), but their descriptions include explicit disambiguation guidance, so an agent can correctly choose. clipform_get_guide and clipform_get_workflow are also similar but clearly differentiated.

Naming Consistency4/5

Tool names follow a consistent clipform_<verb>_<noun> pattern throughout, e.g., clipform_create_form, clipform_add_node, clipform_update_node, clipform_delete_node. Minor deviations exist: clipform_whoami is not verb_noun, and get_more_tools lacks the clipform_ prefix, but these are edge cases and the overall convention is highly predictable.

Tool Count3/5

34 tools is on the heavy side for a single MCP server. The server covers a broad domain (form creation, node editing, media management, video rendering, TTS, search, guidance, imports, responses), so the count is defensible, but it is above the typical well-scoped range and may add navigation overhead.

Completeness5/5

The tool surface covers the full lifecycle: create/read/update/delete forms and nodes, media upload/attach/delete, multiple render paths with status checking, TTS generation, music/image/video search, form import, response retrieval, and workflow/guide knowledge. The main gap is lack of a direct branching-logic editor (option-based branching is only in the dashboard), but the API consciously documents that limitation and the rest of the lifecycle is complete.