Clipform

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

TableJSON Schema

Name	Required	Description
`node`	Yes	The node to add
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.
`form_id`	Yes	The form UUID (returned by clipform_create_form, not the short share_id from the URL)
`after_node_id`	No	Insert after this node ID. Omit to append before the end screen.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes	Node type that was added
`node_id`	Yes	ID of the created node - pass to update_node / attach_node_media

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 6, 2026
- 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
```

Changed1 schema field changedSep 7, 2026

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"
+]

Changed1 schema field changedSep 4, 2026

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."

Changed2 schema fields changedSep 3, 2026

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"
-}

Changed3 schema fields changedAug 31, 2026

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"
+]

Changed1 schema field changedJul 21, 2026

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"
+]

Changed2 schema fields changedJul 13, 2026

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"

Changed1 schema field changedJul 8, 2026

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"
+}

First observedJul 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real behavioral context beyond them: default append-before-end-screen placement and automatic chain re-linking on linear insert. It does not spell out that repeated calls create duplicate nodes or note any permission requirements, so it is strong but not exhaustive.

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?

Three sentences, all front-loaded and purposeful: purpose, insertion mechanics, then the logic-relinking implication. No filler or restatement of the title.

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 mutation tool with a nested node object, an output schema, and full annotation coverage, the description supplies the key operational facts (positioning, relinking, where to find config schemas). It leaves minor gaps around duplicate-insert semantics and permissions, but nothing that would cause a misinvocation.

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 description coverage is 100%, so the baseline is 3; the description earns more by clarifying default insertion ('Inserted before the end screen by default; after_node_id controls insertion position') and by cross-referencing clipform_create_form and clipform_get_guide for config shapes rather than duplicating them.

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?

States a specific verb and resource ('Add a new node to an existing form') and immediately scopes it with default insertion position, cleanly separating it from siblings like clipform_update_node and clipform_delete_node. It also anchors node typing to clipform_create_form, so an agent knows the shapes before opening a 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?

Gives explicit when/when-not guidance: use this for a simple insert because linear re-linking is automatic and 'you do not need clipform_set_logic', while branching 'still needs an explicit logic write'. It names the alternative tool and the condition that selects it.

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

All Clipform tools Inspect

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.

Add Node

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources