Skip to main content
Glama

add_node

Add a node using a known nodeType from the editor or get_node_definitions. Unknown types can be found with list_available_nodes. Set node data with config. This edits the graph without running generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>",
      "workflowId": "<workflowId>",
      "nodeType": "<nodeType>"
    },
    "name": "add_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOptional custom label for the node
configNoNode configuration/data values
nodeTypeYesType of node to add (e.g., constant_text, media_image, llm_text)
workflowIdYesWorkflow ID
workspaceIdYesThe workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait that this mutates the graph without running generation. However, it says nothing about permissions, validation failures for a bad nodeType, whether the node is inserted at a default position, or what identifiers come back.

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?

Four short sentences, front-loaded with the core action and immediately followed by the prerequisite lookup guidance. No filler, though the choppy structure and the dangling 'Set node data with config' sentence slightly interrupt the flow.

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 mutation tool with no annotations and no output schema, the description is adequate but thin. It omits what the tool returns (presumably a node ID, which connect_nodes would need) and offers no caution about failures or graph side effects.

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 baseline is 3. The description only adds that config carries node data and that nodeType must be a known type, which is marginally useful but largely duplicative of the schema's own descriptions.

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?

"Add a node" gives a clear verb+resource, and the description scopes it to a graph built from known node types. It implicitly separates itself from update_node/connect_nodes/delete_node by emphasizing adding, though it never names those siblings directly.

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?

It explicitly routes the agent: pull nodeType from the editor or get_node_definitions, and fall back to list_available_nodes for unknown types. It also clarifies the operation does not trigger generation. What's missing is guidance on what to do after adding (connect_nodes) or when to prefer update_node over adding.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.