Skip to main content
Glama
dwgx

Blender Copilot MCP Server

by dwgx

anim_delete_keyframe

Delete keyframes from object properties using object name, property path, and frame number. Optionally specify channel index to remove all channels.

Instructions

Delete a keyframe from an object property.

Args: object_name: Target object name data_path: Property path frame: Frame number to delete index: Channel index (-1 = all)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameYes
indexNo
data_pathYes
object_nameYes
Behavior2/5

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

With no annotations provided, the description carries full burden but only states 'Delete a keyframe' without disclosing side effects, prerequisites (e.g., existence of keyframe), or failure modes, making it insufficient for a destructive operation.

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?

The description is extremely concise with a single main sentence and a parameter list, front-loading the action and containing no unnecessary information.

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?

Despite having 4 parameters and no annotations or output schema, the description omits return behavior, error conditions, and how to format parameters like data_path. It does not leverage sibling context to differentiate from similar tools, leaving gaps for reliable agent usage.

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 description lists parameter names with brief explanations (e.g., 'Target object name', 'Frame number to delete'), adding some meaning beyond the schema's bare types and names. However, given 0% schema coverage, more detailed semantics (e.g., data_path format) would improve clarity.

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 'Delete a keyframe from an object property' with a specific verb and resource, effectively distinguishing it from sibling tools like anim_insert_keyframe and anim_clear_all.

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 provides no guidance on when to use this tool versus alternatives such as anim_clear_all or anim_insert_keyframe, leaving the agent without context for proper selection.

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/dwgx/blender-copilot'

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