Skip to main content
Glama

blender_scene

Create, organize, and configure Blender scenes, collections, view layers, lighting, cameras, and render settings.

Instructions

Comprehensive scene management for Blender.

Supports multiple operations through the operation parameter:

  • create_scene: Create a new scene

  • list_scenes: List all scenes in the file

  • clear_scene: Clear all objects from current scene

  • set_active_scene: Set the active scene

  • link_object_to_scene: Link object to a scene

  • create_collection: Create a new collection

  • add_to_collection: Add object to collection

  • set_active_collection: Set the active collection

  • set_view_layer: Set active view layer

  • setup_lighting: Set up scene lighting

  • setup_camera: Set up scene camera

  • set_render_settings: Configure render resolution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoPosition as [x, y, z] for camera/light
rotationNoRotation as [x, y, z] for camera
operationNoScene operation typelist_scenes
layer_nameNoName for view layer operations
light_typeNoType of light (SUN, POINT, SPOT, AREA)SUN
scene_nameNoName for scene operationsNewScene
object_nameNoName of object for linking operations
resolution_xNoRender width in pixels
resolution_yNoRender height in pixels
collection_nameNoName for collection operations

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior1/5

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

The annotation states destructiveHint=false, but the description explicitly lists 'clear_scene: Clear all objects from current scene', which is a destructive operation. This is a direct contradiction between the description and the annotations. Additionally, the description does not disclose other behavioral traits such as parameter requirements per operation or side effects beyond the operation list.

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?

The description is efficiently structured with a one-sentence summary followed by a bulleted list of operations. Each line is concise and adds direct information. There is no unnecessary verbosity, and the front-loaded summary provides immediate orientation.

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?

Despite having an output schema and comprehensive parameter descriptions, the tool description does not explain which parameters apply to which operations. For example, setup_camera likely requires 'location' and 'rotation', but this mapping is absent. The description also omits information about default behaviors, prerequisites, or how the output varies by operation, making it incomplete for a tool with this complexity.

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?

The input schema already has 100% description coverage for all 10 parameters, with clear descriptions like 'Position as [x, y, z] for camera/light'. The tool description adds no additional parameter semantics beyond listing the operations, which map to the 'operation' enum already present in the schema. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 clearly identifies the tool as a comprehensive scene manager for Blender and enumerates 12 specific operations with brief explanations, such as 'clear_scene: Clear all objects from current scene'. This makes the tool's purpose unmistakable and distinguishes it from sibling tools that focus on singular operations.

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?

The description does not provide any guidance on when to use this tool versus the many sibling tools that appear to cover the same operations (e.g., create_scene, list_scenes, set_active_scene, create_collection). No exclusions or alternative recommendations are given, leaving the agent to infer when the dispatcher-style tool is preferred over individual tools.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server