Skip to main content
Glama
Sign In

Clipform

by io.github.Clipform
OverviewDiscussionsAdmin

Add Node

clipform_add_node

Add a new node to an existing form. Inserted before the end screen by default; after_node_id controls insertion position. Inserting into a linear flow automatically re-links the chain (the node before the insertion point points to the new node, which points to what followed) - you do not need clipform_set_logic for a simple insert. Branching still needs an explicit logic write. Node types and config schemas match clipform_create_form.

Input Schema

NameRequiredDescriptionDefault
nodeYesThe node to add
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)
after_node_idNoInsert after this node ID. Omit to append before the end screen.

Output Schema

NameRequiredDescriptionDefault
typeYesNode type that was added
node_idYesID of the created node - pass to update_node / attach_node_media

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / node / properties / options / description
      Previous value: -"Answer options. choice: required, min 1, max 12, max 6 when option_display is \"letters\", content max 36 chars button: required, min 1, max 1, content max 28 chars"New value: +"Answer options. choice: required, min 1, max 12, max 6 when option_display is \"letters\", content max 80 chars button: required, min 1, max 1, content max 28 chars"
  2. Changed1 schema field changed
    • changedInput schema / properties / node / properties / options / description
      Previous value: -"Answer options. choice: required, min 1, max 6, content max 36 chars button: required, min 1, max 1, content max 28 chars"New value: +"Answer options. choice: required, min 1, max 12, max 6 when option_display is \"letters\", content max 36 chars button: required, min 1, max 1, content max 28 chars"
  3. Changed1 schema field changed
    • changedInput schema / properties / node / properties / type / enum
      Previous value: -[
-  "choice",
-  "open",
-  "details",
-  "camera",
-  "payment",
-  "button",
-  "redirect",
-  "file_download",
-  "end_screen"
-]New value: +[
+  "choice",
+  "open",
+  "details",
+  "draw",
+  "camera",
+  "payment",
+  "button",
+  "redirect",
+  "file_download",
+  "end_screen"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / node / properties / type / enum
      Previous value: -[
-  "choice",
-  "open",
-  "details",
-  "payment",
-  "button",
-  "redirect",
-  "file_download",
-  "end_screen"
-]New value: +[
+  "choice",
+  "open",
+  "details",
+  "camera",
+  "payment",
+  "button",
+  "redirect",
+  "file_download",
+  "end_screen"
+]
  5. Changed4 schema fields changed
    • addedInput schema / properties / form_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / node / additionalProperties
      Removed value: -false
    • addedInput schema / properties / node / properties / config / propertyNames
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / node / properties / options / items / additionalProperties
      Removed value: -false
  6. Changed1 schema field changed
    • changedInput schema / properties / node / 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"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / node / 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."
  8. Changed2 schema fields changed
    • addedInput schema / properties / node / 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 / node / 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"
-}
  9. 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",
-  "node"
-]New value: +[
+  "form_id",
+  "node",
+  "context"
+]
  10. Changed1 schema field changed
    • changedInput schema / properties / node / 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"
+]
  11. Changed2 schema fields changed
    • changedInput schema / properties / node / 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 / node_id / description
      Previous value: -"ID of the created node - pass to update_node / upload_node_media"New value: +"ID of the created node - pass to update_node / attach_node_media"
  12. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "node_id": {
+      "description": "ID of the created node - pass to update_node / upload_node_media",
+      "type": "string"
+    },
+    "type": {
+      "description": "Node type that was added",
+      "type": "string"
+    }
+  },
+  "required": [
+    "node_id",
+    "type"
+  ],
+  "type": "object"
+}
  13. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=false, destructive=false), it discloses a non-obvious side effect: inserting into a linear flow automatically re-links the chain so the prior node points to the new one. That is exactly the kind of behavioral detail annotations cannot convey.

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?

Four short sentences, front-loaded with the action and default position, then the re-linking rule, then the logic exception. No filler or restatement of the name.

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?

Given a nested node object with a 10-value type enum, an arbitrary config object, and an existing output schema, the description covers insertion semantics and offloads type-specific config to clipform_create_form plus guide references. It does not mention failure modes (e.g., invalid after_node_id, node limits), which keeps it just short of complete.

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 description adds real meaning for after_node_id (omit to append before the end screen) and clarifies that node types and config schemas match clipform_create_form rather than being documented here. This lifts it above the schema-only baseline.

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 names a specific verb and resource ('Add a new node to an existing form') and immediately scopes behavior: default insertion is before the end screen, and after_node_id controls position. An agent can distinguish this from clipform_update_node or clipform_create_form without opening any schema.

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

Usage Guidelines5/5

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

It explicitly routes the agent away from a sibling: 'you do not need clipform_set_logic for a simple insert' but 'Branching still needs an explicit logic write.' It also points to clipform_create_form for node types and clipform_get_guide for craft guidance, giving clear when-to-use context.

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