Arbo

bulk_create_nodes

Create multiple pages at once from a tree structure. Ideal for generating a full sitemap with zoning, entry points, CTAs and tags.

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": {
      "project_id": "<project_id>",
      "nodes": "<nodes>"
    },
    "name": "bulk_create_nodes"
  }
}

Input Schema

Name	Required	Description	Default
`nodes`	Yes	Flat list of nodes with temp_id references for parent-child relationships (500 max)
`project_id`	Yes	The project ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

changedInput schema / properties / nodes / description

Previous value: -"Flat list of nodes with temp_id references for parent-child relationships"New value: +"Flat list of nodes with temp_id references for parent-child relationships (500 max)"

addedInput schema / properties / nodes / maxItems
```
Added value: +500
```

First observedSep 25, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. Beyond the word 'Create', it says nothing about atomicity (does a partial failure roll back?), permissions required, the 500-node ceiling, or response shape for a large mutation.

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?

Two tight sentences with the core action front-loaded and the use case second. Every clause earns its place; no restating of the tool name or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a bulk mutation tool with no annotations and no output schema, so the description is the only place behavioral guarantees can live — and it omits partial-failure semantics, ordering/validation of temp_id references, and what the caller gets back. Adequate for identifying the tool, insufficient for calling it safely.

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%, and the deeply nested node schema documents temp_id/parent_temp_id, seo, zoning_blocks and entry_points thoroughly. The description adds no format or constraint detail beyond echoing those field names, so the baseline 3 applies.

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?

States a specific verb and resource ('Create multiple pages at once') and adds the mechanism ('from a tree structure'), which clearly separates it from the singular sibling create_node. It stops short of naming that sibling explicitly, so an agent must infer the bulk-vs-single distinction from the name.

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

Usage Guidelines3/5

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

'Ideal for generating a full sitemap' gives a concrete usage scenario, implying this is the right choice for whole-site generation rather than incremental edits. However, it names no alternatives and states no when-not-to-use condition (e.g. use create_node for a single page).

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

All Arbo 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.

Resources

Need Help?