Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

edit_camera

Configure an existing Blender camera's lens, projection, clipping, depth of field, and 3D transform, and set it active to adjust scene framing and camera behavior.

Instructions

Configure properties and transform of an existing camera in the active Blender scene. Updates focal length (lens), projection type (PERSP, ORTHO, PANO), orthographic scale, clipping planes (clip_start, clip_end), sensor dimensions (sensor_width, sensor_height, sensor_fit), shift (shift_x, shift_y), depth of field (use_dof, focus_distance, aperture_fstop), 3D transform (location, rotation), and active camera assignment.

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": "edit_camera"
  }
}

Input Schema

NameRequiredDescriptionDefault
dofNoDepth of field settings.
lensNoFocal length in millimeters (1.0 to 5000.0).
nameYesName of the existing camera object to configure.
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 for grouping related scene mutation operations.
use_dofNoEnable depth of field.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent. Mutations must be approved through a trusted approval mechanism.
clip_endNoFar clipping distance in Blender units (> clip_start).
locationNo3D world location coordinates [x, y, z].
clip_startNoNear clipping distance in Blender units (> 0.0001).
sensor_fitNoSensor fit mode: 'AUTO', 'HORIZONTAL', or 'VERTICAL'.
set_activeNoWhether to set this camera as the active scene camera.
camera_nameNoAlias for name of the camera object.
camera_typeNoCamera projection type: 'PERSP' (Perspective), 'ORTHO' (Orthographic), or 'PANO' (Panoramic).
ortho_scaleNoOrthographic scale factor for ORTHO cameras (> 0.001 to 10000.0).
target_nameNoAlias for name of the camera object.
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 clear focus object.
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 remove tracking constraint.
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?

No annotations are supplied, so the description carries the full disclosure burden. It does usefully enumerate which properties are mutated, but omits key behavioral facts: whether unspecified properties are preserved, what happens if the camera name is not found, that mutations may require trusted approval (an 'approved' parameter exists), and what the call returns.

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?

A single front-loaded sentence that opens with the action and scope, then groups the affected properties compactly. The enumeration is long but every clause names real capabilities; only the (PERSP, ORTHO, PANO) and example values are slightly redundant with the schema.

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 27-parameter mutation tool with a nested DOF object, no annotations, and no output schema, the description is adequate but leaves gaps: alias parameters, tracking constraint behavior, composition guide toggle, and task/approval semantics go unmentioned. The safety and failure-mode story is entirely missing.

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 description coverage is 100%, so the schema already documents each parameter, making 3 the baseline. The description adds conceptual grouping (transform vs. lens vs. DOF vs. sensor) and parenthetical enum hints, but never explains the many aliases (camera_name, target_name, focal_length, camera_type) or track_to_object and show_composition_thirds.

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?

States a specific verb ('Configure') and resource ('existing camera in the active Blender scene') and enumerates the property groups touched, which is well beyond the title. It does not, however, distinguish itself from the sibling 'configure_camera' or explain how it relates to 'switch_camera', so an agent cannot fully disambiguate from the text alone.

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?

'existing camera' implicitly signals this is for modification rather than creation (vs 'create_camera'), and the set_active option hints at camera switching. But there is no explicit statement of when to use this versus configure_camera, nor any prerequisite such as the camera having to exist or the scene being active.

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