Skip to main content
Glama

blender_get_objects

Read-onlyIdempotent

List Blender scene objects with filters for type, collection, selection, visibility, or name pattern. Returns name and type to understand scene contents.

Instructions

List objects in the Blender scene with optional filters. Returns name and type for each object by default.

Use this as the first call to understand what exists in a scene.

Do NOT use for: detailed object properties (use blender_get_object_data), material listing (use blender_get_materials), or collection tree (use blender_get_collections).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
type_filterNoFilter by object type (MESH, LIGHT, CAMERA, CURVE, EMPTY, etc.).
collectionNoFilter by collection name. Only returns objects in this collection.
selected_onlyNoIf true, only return currently selected objects.
visible_onlyNoIf true, only return objects visible in viewport.
name_patternNoGlob pattern to filter by name (e.g. 'SM_*' or '*_high').
include_locationNoInclude location [x, y, z] for each object (increases response size).
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. Description adds useful context: default return fields (name and type) and effect of include_location parameter.

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?

Three sentences, front-loaded with purpose, then usage guidance. No unnecessary words. Highly efficient.

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

Completeness5/5

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

Describes return values (name and type by default, location optionally) and differentiates from siblings. No gaps given the simplicity of the tool.

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 baseline is 3. Description does not significantly extend parameter semantics beyond what schema already provides, but it's adequate.

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?

Description clearly states it lists objects with optional filters, returns name and type, and distinguishes from sibling tools like blender_get_object_data and blender_get_collections.

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 recommends using this as the first call to understand the scene and lists alternatives for specific tasks, providing clear when-to-use and when-not-to-use guidance.

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