Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_compositor

Build and edit Blender compositing node trees to add post-processing effects, configure render passes, and manage composite outputs without manual node setup.

Instructions

Manipulate Blender's compositing node tree for post-processing effects, bloom/glare, denoising, color grading, render passes, and composite outputs in Blender 5.2.2 LTS.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "manage_compositor"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoCompositing action to perform.inspect
inputsNoOptional initial socket values for node creation.
passesNoDictionary of pass names to booleans for configure_render_passes (e.g. {'z': true, 'normal': true, 'diffuse': true, 'glossy': true, 'ao': true, 'shadow': true, 'emission': true, 'environment': true, 'mist': true}).
task_idNoOptional task or workflow identifier.
to_nodeNoDestination node name for connection/disconnection.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoOptional [x, y] node placement coordinates.
from_nodeNoSource node name for connection/disconnection.
node_nameNoName or identifier of the node for creation, removal, or property updates.
node_typeNoCompositor node type (e.g. CompositorNodeGlare, CompositorNodeDenoise, CompositorNodeBlur, CompositorNodeColorBalance, CompositorNodeCryptomatteV2).
to_socketNoDestination input socket name or index.
scene_nameNoOptional scene name (defaults to active scene).
from_socketNoSource output socket name or index.
property_nameNoProperty name when action is set_property.
property_valueNoValue to assign when action is set_property.
expected_snapshot_idNoOptional snapshot identifier for optimistic concurrency control (stale-state protection).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and falls well short. It never states that actions like remove_node and disconnect mutate or destroy existing node graph state, whether changes are reversible, or what state prerequisites (enabled compositing, existing scene) apply.

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?

A single front-loaded sentence with no filler or redundancy. The trailing enumerations of effect types and the version string are somewhat decorative, but the sentence is efficient overall.

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?

For a 16-parameter tool with nine distinct actions, no annotations, and no output schema, the description is far too thin. It does not enumerate the actions, describe what inspect or list_nodes returns, or explain the destructive remove/disconnect modes, leaving an agent unable to invoke it reliably.

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 every one of the 16 parameters is already documented in the schema, establishing the baseline of 3. The description adds no parameter meaning beyond the schema — it does not mention the action enum values, node naming conventions, or the snapshot/concurrency parameter.

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?

The description names a specific verb and resource ('Manipulate Blender's compositing node tree') and scopes it to post-processing effects including bloom/glare, denoising, color grading, and render passes. It does not, however, distinguish this tool from siblings like manage_compositor_nodes, configure_compositor, or inspect_compositor_pipeline, which appear to overlap heavily.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no mention of the nine action modes the tool supports. An agent has no basis in the description for choosing this tool over manage_compositor_nodes or configure_compositor.

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

Deploy Server

Other Tools