Skip to main content
Glama

Add Surface Element

add_surface_element

Add shapes, connectors, text, or groups to the AFFiNE edgeless canvas to build diagrams programmatically. Supports styling and ignoring inapplicable fields.

Instructions

Add a shape, connector, text, or group to the AFFiNE edgeless canvas surface. Shapes support rect/ellipse/diamond/triangle with fill, stroke, and text. Connectors draw arrows between shapes (by id) or between absolute points. Use for building diagrams programmatically. Style fields that don't apply to the chosen element type are reported in the response 'ignored' list (mirrors update_surface_element).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX position on canvas (shape/text; default 0).
yNoY position on canvas (shape/text; default 0).
modeNoConnector mode: 0=straight, 1=orthogonal (elbow), 2=curve (default 2). Connector only.
textNoText content (shape/text) or connector label. Replaces existing Y.Text on update.
typeYesElement type
colorNoText color. Shape default `#000000` — keep unless the fill is dark, then pass a contrasting hex. Canvas text default `--affine-text-primary-color` (theme-adaptive). Shape/text.
docIdYesDocument ID
indexNoBlockSuite fractional-index string controlling z-order. On add, defaults to a key above every existing element's index (new elements render on top). On update, replaces the stored value — pass a key less than some existing index to send-to-back, or greater to bring-to-front. Use the value returned by list_surface_elements to pick a specific position.
labelNoConnector label (stored as text on the connector). Connector only.
titleNoGroup title. Group only.
widthNoWidth (shape default 100, text default 200).
filledNoWhether shape is filled (default true). Shape only.
heightNoHeight (shape default 100, text default 30).
radiusNoCorner radius for rect (0.1 = rounded). Shape only.
strokeNoConnector stroke color (default '--affine-text-primary-color' — theme-adaptive, near-black in light / near-white in dark). Accepts any CSS color or AFFiNE palette token. Connector only.
childrenNoChild element ids. Group only.
fontSizeNoFont size (shape default 20, text default 16). Shape/text.
sourceIdNoConnector source element id. Connector only.
targetIdNoConnector target element id. Connector only.
fillColorNoFill color. Prefer the `--affine-palette-shape-<color>` family (yellow/orange/red/magenta/purple/navy/blue/green/teal/grey/white/black). These are fixed colors — AFFiNE shape colors are not theme-adaptive by design. Shape only.
shapeTypeNoShape type (default rect). Shape only.
fontWeightNoFont weight (shape default 600, text default 400). Shape/text.
strokeColorNoStroke color. Prefer the `--affine-palette-line-<color>` family (same color names as fillColor). Fixed colors, not theme-adaptive. Shape only.
strokeStyleNoStroke style. Shape/connector.
strokeWidthNoStroke width (default 2). Shape/connector.
workspaceIdNoWorkspace ID (optional if default set)
sourcePositionNoSource [x,y]: relative [0-1] if sourceId set, absolute otherwise. Connector only.
targetPositionNoTarget [x,y]: relative [0-1] if targetId set, absolute otherwise. Connector only. When both source/target are bound by id and neither position is provided, endpoints snap to the BlockSuite side-midpoint facing the other endpoint so connectors flow in a clear direction. Pass [0.5,0] top, [0.5,1] bottom, [0,0.5] left, [1,0.5] right to force a specific side.
rearEndpointStyleNoRear endpoint style (default Arrow). Connector only.
frontEndpointStyleNoFront endpoint style (default None). Connector only.
Behavior4/5

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

Annotations already indicate mutability and non-destructiveness. Description adds that inapplicable fields are reported in the 'ignored' list and explains element-type-specific behaviors (shapes vs connectors). No contradictions.

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?

Three sentences, each earning its place: purpose, detailed feature description, and usage guidance. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 30 parameters and no output schema, the description provides a high-level map of element types and key behavior. It covers the essential behavioral nuance (ignored list) but could elaborately tie all parameters together, though the schema descriptions are rich.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage. Description adds context beyond schema by explaining shape capabilities, connector drawing modes, and the ignored field behavior. Adds value despite high schema coverage.

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 verb 'Add' and the resource 'shape, connector, text, or group to the AFFiNE edgeless canvas surface'. It distinguishes from sibling tools like 'update_surface_element' and 'delete_surface_element' by focusing on creation.

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?

Explicitly recommends usage 'for building diagrams programmatically' and references 'update_surface_element' for ignored list behavior. Could more directly state when not to use, but context is clear.

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/DAWNCR0W/affine-mcp-server'

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