Skip to main content
Glama

Clipform

by io.github.Clipform
OverviewDiscussionsAdmin

Update Node

clipform_update_node
DestructiveIdempotent

Update one or more existing nodes' text, type, config, or options. Pass multiple updates in one call instead of separate tool calls. Requires node IDs (returned by clipform_create_form, clipform_add_node, or clipform_get_form). Does not change node positions in the flow. All type definitions and config schemas are derived from @vid-master/config (node-types).

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)
updatesYesOne or more node updates to apply

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesOne result per requested update, in order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / updates / items / properties / type / enum
      Previous value: -[
-  "choice",
-  "open",
-  "details",
-  "button",
-  "redirect",
-  "file_download",
-  "end_screen"
-]New value: +[
+  "choice",
+  "open",
+  "details",
+  "payment",
+  "button",
+  "redirect",
+  "file_download",
+  "end_screen"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / updates / 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."
  3. Changed2 schema fields changed
    • addedInput schema / properties / updates / 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 / updates / 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"
-}
  4. 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",
-  "updates"
-]New value: +[
+  "form_id",
+  "updates",
+  "context"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / updates / 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. Changed1 schema field changed
    • changedInput schema / properties / updates / items / properties / config / description
      Previous value: -"Type-specific configuration keyed by node type. Omit to use defaults. Per-type keys, shapes, and defaults are listed in the clipform_create_form description; craft guidance via clipform_get_guide."New value: +"Type-specific configuration keyed by node type. Omit to use defaults. Per-type keys, shapes, and defaults are listed in the clipform_create_form description; craft guidance via clipform_get_guide. Merged shallowly into the stored config - only the keys you pass are changed. Set a key to null to delete it; nested objects are replaced wholesale. When type is changed in the same call, config replaces the stored configuration instead of merging."
  7. Changed1 schema field changed
    • changedInput schema / properties / updates / 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"
+]
  8. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "results": {
+      "description": "One result per requested update, in order",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "error": {
+            "type": "string"
+          },
+          "node_id": {
+            "type": "string"
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "warnings": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "node_id",
+          "ok"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  9. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already indicate destructive and idempotent behavior. The description adds precise details about config merge semantics, null deletion, wholesale replacement of nested objects, and full config replacement on type change, which clarifies the destructive nature.

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?

The description is tight and information-dense without filler. Each sentence carries essential guidance, and parameter descriptions are detailed but relevant.

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 complex update tool, the description covers batching, ID provenance, config behavior, option constraints, and cross-references to authoritative sources. An output schema exists, so return-value documentation is not required.

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?

Schema coverage is 100%, and parameter descriptions add substantial guidance beyond the schema: merge behavior, option scoring semantics, correct-answer marking, and references to create_form/get_guide for type-specific config. This is far beyond a baseline schema restatement.

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?

Clearly states the tool updates existing nodes and lists the mutable aspects (text, type, config, options). It is distinct from sibling tools like clipform_add_node or clipform_delete_node, and references how to obtain node IDs.

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?

Explicitly says to pass multiple updates in one call instead of separate calls and notes that node IDs come from specific prior tools. It could mention alternatives like add/delete more directly, but the intent is clear.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources