Skip to main content
Glama
AndresMuelas2004

tldraw MCP Server

tldraw_create_arrow

Add arrows to a canvas with straight or curved paths and automatic binding to shapes for clear connections.

Instructions

Create an arrow shape. Supports straight, curved (bend), and auto-binding to shapes. Set startBinding/endBinding to connect the arrow to shapes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position on canvas
yYesY position on canvas
bendNoBend amount (0=straight, positive=curve right, negative=curve left)
dashNoDash styledraw
endXNoEnd point X (relative to shape position)
endYNoEnd point Y (relative to shape position)
fillNoFill stylenone
fontNoFont for labeldraw
sizeNoSize stylem
textNoArrow label text
colorNoArrow colorblack
pageIdYesTarget page ID (e.g. 'page:xxx')
startXNoStart point X (relative to shape position)
startYNoStart point Y (relative to shape position)
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)
endBindingNoBind end to a shape
labelColorNoLabel colorblack
arrowheadEndNoEnd arrowhead typearrow
startBindingNoBind start to a shape
arrowheadStartNoStart arrowhead typenone
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It explains arrow curvature and binding but omits side effects (e.g., immediate addition to page, return value), required permissions, or limitations, leaving significant behavioral gaps.

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 two sentences long, immediately states the main action, and includes essential features without extraneous information, achieving high conciseness and structure.

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?

Given 23 parameters with nested objects like startBinding and no output schema, the description is too brief. It fails to explain how to use complex parameters, what the tool returns, or typical usage patterns, leaving the agent underinformed.

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 the baseline is 3. The description adds context for bend and binding parameters but does not significantly enhance the schema's already detailed parameter descriptions, earning a baseline score.

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 tool creates an arrow shape, specifying it supports straight, curved, and auto-binding to shapes, which distinguishes it from other shape creation tools like tldraw_create_geo or tldraw_create_line.

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 mentions supports for bend and binding, implying when to use these features, but it lacks explicit guidance on when to use this tool versus alternatives or prerequisites, such as needing a page or shape IDs.

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