Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_camera

Creates a new camera in the active Blender scene with configurable lens, clipping planes, sensor, and transform, and can set it as the active camera.

Instructions

Create a new camera in the active Blender scene with configurable focal length (lens), clipping planes, sensor width, and world transform. Can automatically set the new camera as active.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
dofNoDepth of field settings.
lensNoFocal length in millimeters (1.0 to 5000.0).
nameYesUnique name for the new camera object.
typeNoAlias for camera projection type: 'PERSP', 'ORTHO', or 'PANO'.
shift_xNoHorizontal camera shift (-10.0 to 10.0).
shift_yNoVertical camera shift (-10.0 to 10.0).
task_idNoOptional task or workflow identifier.
use_dofNoEnable depth of field.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
clip_endNoFar clipping distance in Blender units.
locationNo3D world coordinates [x, y, z] for camera placement.
clip_startNoNear clipping distance in Blender units (> 0.0001).
sensor_fitNoSensor fit mode: 'AUTO', 'HORIZONTAL', or 'VERTICAL'.AUTO
set_activeNoWhether to assign this camera as the active scene camera.
camera_typeNoCamera projection type: 'PERSP' (Perspective), 'ORTHO' (Orthographic), or 'PANO' (Panoramic).PERSP
ortho_scaleNoOrthographic scale factor for ORTHO cameras (> 0.001 to 10000.0).
focal_lengthNoFocal length in millimeters (alias for lens).
focus_objectNoTarget object name for dynamic depth-of-field focus point. Pass null or empty string to disable focus target.
sensor_widthNoCamera sensor width in millimeters (1.0 to 200.0).
sensor_heightNoCamera sensor height in millimeters (1.0 to 200.0).
aperture_fstopNoAperture f-stop number.
focus_distanceNoFocus distance in meters.
rotation_eulerNoEuler rotation angles in radians [rx, ry, rz].
track_to_objectNoTarget object name for camera to track using a TRACK_TO constraint. Pass null or empty string to disable tracking.
show_composition_thirdsNoDisplay rule-of-thirds composition guide grid in the camera viewport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully adds that the camera is created 'in the active Blender scene' and that it can auto-set as active, but it doesn't disclose side effects (name collisions, what happens with existing active camera, tracking constraint creation). The deprecated approved flag is only explained in the schema.

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?

Two sentences, front-loaded with the core action and with no filler. It is efficient but omits several notable capabilities (DOF, tracking, sensor fit), so it is tight rather than complete.

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?

For a 25-param tool with nested DOF objects, enum aliases, and a deprecated approval flag, and with no annotations or output schema, the description is somewhat thin. The schema's full coverage compensates, but it doesn't flag the alias duplication (lens/focal_length, type/camera_type) or the untrusted approved flag.

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 schema already documents all 25 parameters in detail. The description echoes a few parameter categories (lens, clipping, sensor width, transform) but adds no syntax or alias disambiguation (e.g., lens vs focal_length, camera_type vs type) beyond what the schema states.

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 states a specific verb and resource: 'Create a new camera in the active Blender scene,' and lists the configurable capabilities (focal length, clipping planes, sensor width, world transform). This clearly distinguishes the tool from siblings like configure_camera/edit_camera/switch_camera, but it never names those alternatives.

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

Usage Guidelines3/5

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

Usage is only implied: 'Create a new camera' suggests use for new camera creation, and 'Can automatically set the new camera as active' gestures at the default active behavior. There is no explicit when-to-use vs configure_camera/edit_camera guidance and no exclusion conditions.

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