Skip to main content
Glama

Clipform

by io.github.Clipform

Update Clipform

clipform_update_form
DestructiveIdempotent

Update a form's title, publish status, settings, or tags. Only sends fields that are provided - omitted fields remain unchanged. AI-PROTECTED parameters have restrictions noted in their descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoReplace all tags on this form. Pass the full desired set (e.g. ['quiz', 'trivia', 'slug:elephants']). Omit to leave tags unchanged.
titleNoNew form title
authorNoAI-PROTECTED: Only set when the user explicitly provides an author name. Set null to clear.
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)
is_liveNoSetting true publishes/republishes the snapshot respondents see. Forms are live from creation, but edits and media attached AFTER creation are not visible until you re-send true - republishing is the expected final step of a build, never skip it after attaching media. Setting false takes the form offline (keeps the last published snapshot) - AI-PROTECTED: only take a form offline when the user explicitly asks.
logo_urlNoAI-PROTECTED: Only set when the user explicitly provides a logo URL. Set null to clear.
brand_nameNoAI-PROTECTED: Custom brand name shown in footer. Only set when user explicitly provides.
descriptionNoSEO description (meta description, og:description). Set null to clear.
font_familyNoAI-PROTECTED: Only set when the user explicitly requests a specific font.
total_stepsNoOverride the total step count shown in the step counter. Set null to auto-calculate.
primary_colorNoPrimary/brand color as 6-digit hex (e.g. '#FF5500'). Used for buttons and accents.
show_brandingNoShow Clipform branding. Set false to remove (Pro plan).
background_colorNoBackground color as 6-digit hex (e.g. '#1A1A2E').
show_step_counterNoShow step counter (e.g. '1/5'). Recommended for quizzes.
disable_back_navigationNoPrevent respondents from going back. Recommended for quizzes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
form_idYesForm UUID
updated_fieldsYesNames of the fields that were changed by this call

Schema Changelog

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

  1. 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: -[
-  "form_id"
-]New value: +[
+  "form_id",
+  "context"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "form_id": {
+      "description": "Form UUID",
+      "type": "string"
+    },
+    "updated_fields": {
+      "description": "Names of the fields that were changed by this call",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "form_id",
+    "updated_fields"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), lowering the description's burden. The description adds value with the 'only sends fields that are provided' guarantee and the AI-PROTECTED pointer, though it stays silent on republish/offline semantics that live in the is_live parameter. No contradiction with annotations.

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?

Two sentences with the verb+resource front-loaded and zero filler. Every sentence earns its place: the partial-update semantic and the AI-PROTECTED pointer are both decision-relevant, though the AI-PROTECTED sentence could arguably be absorbed into the schema note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter mutation tool, the description is short but the surrounding structured data does the heavy lifting: 100% schema coverage, an output schema, and safety-carrying annotations. The main gap is that the choice between update vs. create/delete vs. update_node is left entirely to inference.

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 schema documents all 16 parameters, including AI-PROTECTED restrictions, hex patterns, and the is_live republishing expectation. The description's 'title, publish status, settings, or tags' list groups parameters only at a high level and adds no meaning beyond the schema — 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 — 'Update a form's title, publish status, settings, or tags' — and enumerates the field categories affected. The partial-update note ('Only sends fields that are provided') helps differentiate it from create/delete siblings, though it does not explicitly name an alternative like clipform_update_node.

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?

The description conveys the partial-update semantic — omitted fields remain unchanged — which tells an agent what to expect when updating a subset of fields, and it flags AI-PROTECTED parameters with a pointer to per-field restrictions. It does not explicitly state when to prefer this over clipform_create_form or clipform_update_node, leaving routing to be inferred.

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

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.

Resources