Skip to main content
Glama

Update Surface Element

update_surface_element

Modify a surface element's position, size, text, style, or connector settings. Irrelevant fields are automatically ignored.

Instructions

Partially update a surface element by id. x/y/width/height merge with the element's current xywh (move without resizing, or vice versa). text/label/title replace their Y.Text wholesale. Fields that don't apply to the element's type are reported in the response 'ignored' list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNoWorkspace ID (optional if default set)
docIdYesDocument ID
elementIdYesElement ID to update
xNoX position on canvas (shape/text; default 0).
yNoY position on canvas (shape/text; default 0).
widthNoWidth (shape default 100, text default 200).
heightNoHeight (shape default 100, text default 30).
shapeTypeNoShape type (default rect). Shape only.
radiusNoCorner radius for rect (0.1 = rounded). Shape only.
filledNoWhether shape is filled (default true). Shape 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.
strokeColorNoStroke color. Prefer the `--affine-palette-line-<color>` family (same color names as fillColor). Fixed colors, not theme-adaptive. Shape only.
strokeWidthNoStroke width (default 2). Shape/connector.
strokeStyleNoStroke style. Shape/connector.
textNoText content (shape/text) or connector label. Replaces existing Y.Text on update.
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.
fontSizeNoFont size (shape default 20, text default 16). Shape/text.
fontWeightNoFont weight (shape default 600, text default 400). Shape/text.
sourceIdNoConnector source element id. Connector only.
targetIdNoConnector target element id. Connector only.
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.
modeNoConnector mode: 0=straight, 1=orthogonal (elbow), 2=curve (default 2). Connector only.
frontEndpointStyleNoFront endpoint style (default None). Connector only.
rearEndpointStyleNoRear endpoint style (default Arrow). Connector 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.
labelNoConnector label (stored as text on the connector). Connector only.
childrenNoChild element ids. Group only.
titleNoGroup title. Group only.
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.
Behavior4/5

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

With no annotations, description reveals key behaviors: partial update, merge vs replace, ignored fields. Does not cover permission requirements or side effects, but sufficient for typical use.

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 concise sentences front-loaded with purpose. No wasted words; each sentence adds critical information.

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?

Given 30 parameters and no output schema, the description covers the key update mechanisms and response hint (ignored list). Could mention return value shape, but adequate.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3. Description adds substantial meaning: merge behavior for xywh, replace for text/label/title, and handling of ignored fields. Significantly enhances schema.

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 'Partially update a surface element by id', distinguishing from add/delete siblings. Explains merge vs replace semantics and ignored fields.

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?

Describes the update operation with specific behaviors (merge for xywh, replace for text). Implicitly differentiates from add/delete but lacks explicit exclusion or when-not-to-use guidance.

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