Skip to main content
Glama

blender_scene

Manage Blender scenes: create, clear, list, or set active scenes; link objects; create collections; configure lighting, camera, 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
operationNoScene operation typelist_scenes
scene_nameNoName for scene operationsNewScene
object_nameNoName of object for linking operations
collection_nameNoName for collection operations
layer_nameNoName for view layer operations
light_typeNoType of light (SUN, POINT, SPOT, AREA)SUN
locationNoPosition as [x, y, z] for camera/light
rotationNoRotation as [x, y, z] for camera
resolution_xNoRender width in pixels
resolution_yNoRender height in pixels

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It briefly describes each operation ('Clear all objects from current scene' for clear_scene) but does not detail side effects, permission requirements, error conditions, or what happens to linked data. Some operations (e.g., link_object_to_scene) are vague about whether objects are moved or instanced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise with a lead sentence and a bulleted list of operations. However, it repeats the operation list that is already in the schema, and the list format makes it somewhat lengthy. It could be tightened without losing clarity.

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?

Given the complexity (10 parameters, 12 operations) and the presence of an output schema, the description covers the main functionality but lacks examples, return value descriptions, and error handling info. It is adequate but not thorough.

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 coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond parameter names and defaults; e.g., 'location' is described as 'Position as [x, y, z] for camera/light' which aligns with the schema but does not elaborate on coordinate systems or units.

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 clearly states it is for 'Comprehensive scene management in Blender' and lists 12 distinct operations via the operation parameter. However, it fails to differentiate itself from sibling tools that offer individual operations (e.g., create_scene, list_scenes), which may confuse agents about which tool to use.

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?

No guidance is provided on when to use this aggregated tool versus the separate sibling tools that perform the same operations. There is no discussion of prerequisites, contextual cues, or alternative tools, leaving the agent without decision-making support.

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

Install Server

Other Tools

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