Skip to main content
Glama
Sign In
Blender MCP Ultra

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_marker

Delete a named timeline marker from Blender's timeline. Specify the marker name, and it is removed immediately.

Instructions

Remove a timeline marker.

Args: marker_name: Name of the marker to remove.

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": {
      "marker_name": "<marker_name>"
    },
    "name": "remove_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
marker_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It clearly communicates the destructive nature of the action ('Remove'), but it does not disclose whether removal is permanent, what happens when the marker does not exist, or whether related animation data is affected.

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?

The description is appropriately short and front-loaded with the core action. The Args block is slightly redundant with the input schema but does not add meaningful clutter.

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 simple one-parameter removal tool, the description is mostly sufficient: it names the operation and the argument. It omits error behavior and whether removal is irreversible, which an agent may need to recover from failed or unexpected calls.

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 0%, so the description must compensate. The Args section explains that marker_name is the name of the marker to remove, which is slightly more than the schema's bare title. However, it adds no detail on formatting, uniqueness, case sensitivity, or required marker existence.

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 states a specific verb ('Remove') and a specific resource ('a timeline marker'). This clearly distinguishes the tool from siblings like add_marker and set_animation_range without needing to inspect schemas.

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?

The intended use is implied: use this tool when a named timeline marker should be removed. However, there is no explicit guidance about when not to use it, prerequisites such as the marker needing to exist, or alternatives like add_marker.

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