Skip to main content
Glama

blender_scene

Manage Blender scenes, collections, and view layers; set up lighting, camera, and render settings for 3D workflows.

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
Behavior2/5

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

No annotations are provided, so the description alone must convey behavioral traits. It lists operations but fails to disclose critical aspects such as potential destructive actions (e.g., clear_scene), required permissions, or side effects. This is insufficient for a tool with multiple operations.

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 structured with a brief header followed by a bulleted list of operations. It is moderately concise but could be more succinct by grouping related operations or removing redundant phrasing.

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?

The tool has 10 parameters and 12 operations, yet the description omits important context such as return values (despite an output schema existing), error handling, or behavior for edge cases. For a complex tool, this is inadequate.

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 provides descriptions for all 10 parameters (100% coverage). The description adds minimal extra meaning beyond the schema, such as listing operation types and noting parameter purposes (e.g., 'Position as [x,y,z]'). This meets the baseline but does not exceed it.

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 'scene management' and lists 12 specific operations, making the purpose evident. However, it does not distinguish itself from sibling tools like create_scene or clear_scene, which perform similar tasks.

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 lists operations but provides no guidance on when to use this tool versus the many sibling tools (e.g., create_scene, clear_scene). There is no mention of prerequisites, alternatives, or context for choosing this tool over individual ones.

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