Skip to main content
Glama

blender_create_object

Create any object type in Blender—mesh, light, camera, curve, empty, armature, or text—and link it to a collection.

Instructions

Create a new object in the Blender scene. Supports mesh primitives, lights, cameras, curves, empties, armatures, and text objects. Automatically linked to the specified collection.

Use this when: you need to add a new object to the scene.

Do NOT use for: modifying existing objects (use blender_modify_object), adding modifiers (use blender_manage_modifier), assigning materials (use blender_manage_material).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new object.
object_typeNoType of object to create.MESH
primitiveNoMesh primitive shape. Only for object_type=MESH.
sizeNoSize of mesh primitive in Blender units.
segmentsNoSegments for sphere/cylinder/cone/torus.
light_typeNoLight type. Only for object_type=LIGHT.POINT
energyNoLight energy in watts. Only for LIGHT.
colorNoLight color [r,g,b] range 0-1. Only for LIGHT.
lensNoCamera focal length in mm. Only for CAMERA.
clip_startNoCamera near clip. Only for CAMERA.
clip_endNoCamera far clip. Only for CAMERA.
set_active_cameraNoSet as active scene camera. Only for CAMERA.
curve_typeNoSpline type. Only for CURVE.BEZIER
bodyNoText content. Only for TEXT.
extrudeNoExtrude depth for TEXT.
locationNo3D position [x, y, z].
rotationNoEuler rotation [x, y, z] in radians.
scaleNoScale [x, y, z].
collectionNoCollection to link to. Uses scene collection if omitted.
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds context about automatic collection linking and implies state changes. However, it does not clarify behavior on repeated calls (idempotentHint=false) or potential side effects.

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?

Two short paragraphs: first states core purpose and supported types, second gives usage guidelines. No wasted words, front-loaded with key information.

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

Completeness4/5

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

Given 19 parameters and no output schema, the description covers the overall purpose well but does not specify what the tool returns (e.g., the created object). However, the schema and guidelines compensate for most needs.

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 baseline is 3. The description mentions supported object types but does not add meaning beyond parameter names and descriptions already in the schema. No additional parameter context.

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 states the action (create a new object), lists supported types (mesh, light, camera, etc.), and mentions automatic collection linking. This distinguishes it from sibling tools like blender_modify_object.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use (adding a new object) and when-not-to-use with specific alternative tools (blender_modify_object, blender_manage_modifier, blender_manage_material). No ambiguity.

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/ageless-h/blender-mcp'

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