Skip to main content
Glama
AndresMuelas2004

tldraw MCP Server

tldraw_create_frame

Creates a frame shape as a container for organizing other shapes on a tldraw canvas, enabling structured layouts by reparenting shapes into it.

Instructions

Create a frame shape. Frames act as containers — other shapes can be reparented into them using tldraw_reparent_shapes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hNoFrame height
wNoFrame width
xYesX position on canvas
yYesY position on canvas
nameNoFrame label
pageIdYesTarget page ID (e.g. 'page:xxx')
opacityNoOpacity from 0 to 1 (default 1)
isLockedNoWhether the shape is locked (default false)
parentIdNoParent frame or group ID for nesting
rotationNoRotation in radians (default 0)
Behavior2/5

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

No annotations provided, so description carries full burden. It only reveals container behavior and links to reparenting but omits any side effects, limitations, or details about shape interactions. Lacks depth for a creation tool.

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?

Two concise sentences, each adding value: first defines the core action, second introduces the unique container trait. No wasted words, front-loaded purpose.

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 10 parameters and no output schema, description is very brief. It explains container behavior but does not cover default values, positioning, or how frames integrate with the canvas. Insufficient for a complex shape creation 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 coverage is 100% with all parameters described; description adds no extra parameter meaning beyond stating the tool creates a frame shape. Baseline 3 as per guidelines.

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?

Clearly states 'Create a frame shape' and distinguishes frames as containers that can host other shapes via reparenting, setting it apart from sibling creation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Mentions frames act as containers and specifically references tldraw_reparent_shapes for reparenting, providing context for when to use this tool. However, it does not explicitly contrast with alternatives like tldraw_create_geo or tldraw_group_shapes.

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/AndresMuelas2004/tldraw-mcp-server'

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