Skip to main content
Glama

blender_grease_pencil

Create, draw, animate, and modify Grease Pencil objects with operations for strokes, layers, materials, modifiers, and interpolation.

Instructions

PORTMANTEAU RATIONALE: Consolidates 12 Grease Pencil 2D animation operations into a single tool.

Operations:

  • create: Create a new Grease Pencil object with layer and initial frame

  • draw_stroke: Draw strokes (LINE, BOX, CIRCLE, ARC, CURVE) with color/thickness

  • convert: Convert Grease Pencil to MESH, CURVE, or new GP strokes

  • set_material: Create and assign GP material with stroke/fill color

  • set_layer: Create, reorder, lock, toggle visibility of GP layers

  • animate_stroke: Keyframe stroke properties (location, rotation, scale) over time

  • onion_skinning: Enable/disable onion skin with before/after frame count

  • add_modifier: Apply GP modifiers (BUILD, NOISE, SIMPLIFY, SMOOTH)

  • fill_region: Fill enclosed stroke regions with color

  • interpolate: Generate in-between frames between two GP frames

  • delete_strokes: Remove strokes from a GP frame by selection type

  • list_layers: List all layers and frame info on a GP object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoThe GP operation to performcreate
nameNoName for new GP object (used by: create)GPencil
gp_objectNoTarget GP object name (used by: draw_stroke, convert, set_material, etc.)
stroke_typeNoLINE|BOX|CIRCLE|ARC|CURVE (used by: draw_stroke)LINE
pointsNoPoint coordinates for LINE/CURVE strokes (used by: draw_stroke)
layer_nameNoTarget layer name (used by: draw_stroke, set_layer, animate_stroke)GP_Layer
frame_numberNoFrame number for drawing (used by: draw_stroke, interpolate)
colorNoRGBA stroke color 0-1 (used by: draw_stroke, set_material)
thicknessNoStroke thickness (used by: draw_stroke)
cyclicNoClose the stroke (used by: draw_stroke)
locationNoPlacement location (used by: create)
target_typeNoMESH|CURVE|GP_STROKES (used by: convert)MESH
keep_originalNoKeep original after conversion (used by: convert)
widthNoBox width (used by: draw_stroke BOX)
heightNoBox height (used by: draw_stroke BOX)
radiusNoCircle radius (used by: draw_stroke CIRCLE)
selection_typeNoALL|VISIBLE|INVERT (used by: delete_strokes)ALL
material_nameNoName for new material (used by: set_material)
fill_colorNoRGBA fill color 0-1 (used by: set_material, fill_region)
modifier_typeNoBUILD|NOISE|SIMPLIFY|SMOOTH (used by: add_modifier)BUILD
modifier_settingsNoJSON string of modifier settings (used by: add_modifier)
svg_pathNoFile path to SVG (used by: import_svg)
before_framesNoFrames before current (used by: onion_skinning)
after_framesNoFrames after current (used by: onion_skinning)
interpolation_framesNoNumber of in-between frames (used by: interpolate)
from_layerNoSource layer for transfer (used by: set_layer)
to_layerNoTarget layer (used by: set_layer)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It briefly describes each operation but omits side effects, prerequisites, permissions, or destructive behaviors (e.g., delete_strokes just says 'remove strokes' without detail).

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 structured with a rationale then bullet list, making it scannable. It is relatively concise given the scope, though a bit long but each part serves a purpose.

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?

Given the complexity (12 operations, 27 parameters) and an existing output schema, the description covers the operations at a high level. However, it lacks behavioral context and usage scenarios, so it is not fully complete for an agent to invoke correctly without additional knowledge.

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. The description groups parameters by operation (e.g., 'used by: draw_stroke') which adds marginal context, but does not provide deeper semantic meaning beyond what the schema already offers.

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 it consolidates 12 Grease Pencil operations and lists each with a brief definition. It distinguishes itself from other Blender tools by focusing specifically on 2D animation with Grease Pencil.

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 description lists operations but provides no explicit guidance on when to use this tool versus sibling tools (e.g., blender_mesh, blender_modifiers). Usage is implied by the operation context, but no 'when not to use' or alternative tools are mentioned.

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/sandraschi/blender-mcp'

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