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

TDQS

A4/5.0
Behavior4/5

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

With annotations already covering idempotent and destructive hints, the description usefully adds a patch behavior: only provided fields are sent and omitted fields remain unchanged. It also warns that AI-PROTECTED parameters carry restrictions, which is meaningful operational context.

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 sentences front-load the primary purpose and then state the two most important behavioral caveats. There is no filler or redundancy with the rich schema.

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?

For a 16-parameter update tool, the description is appropriately high-level because the schema and output schema already carry detailed parameter semantics. It leaves selection guidance to other dimensions but provides sufficient orientation to invoke the tool safely.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the top-level 'Only sends fields that are provided - omitted fields remain unchanged' rule adds cross-cutting semantics that apply to all optional parameters. It clarifies that omission is different from explicit null without repeating individual parameter details.

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 first sentence names the operation (Update), the resource (a form), and the specific mutable aspects (title, publish status, settings, tags), making the tool's role unambiguous. This clearly separates it from creation, deletion, and read operations among the siblings.

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

Usage Guidelines2/5

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

The description gives no guidance about when to choose this tool over clipform_create_form, clipform_get_form, or clipform_import_form, and states no prerequisites or when-not-to-use conditions. The intended use is only implied by the word 'Update'.

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