Skip to main content
Glama

setAnnotation

Update an existing OpenScreen annotation by ID to change its timeline span, type, position, size, text, look, or figure/blur data; only supplied fields change.

Instructions

Change an existing annotation by id: its span (virtual-timeline seconds), its type, its centre (x/y, percent of its box), its size (width/height, arrow and blur only), its text and look (text only: fontSize, color, background, bold, animation), or its figureData / blurData, of which only the keys you pass change. Only the fields you pass are changed. A type change converts it as the editor's type switch does: it stays where it is on screen, a text turned into an arrow or a blur takes the default box, and the text is kept to come back to. A text box is refitted to its text around its centre. Arguments that belong to another kind (width on a text, blurData on an arrow) are refused. A new span that would run into another annotation is refused, naming it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
boldNo
textNo
typeNotext: words on the frame. figure: an arrow. blur: a privacy mask that blurs or pixelates what is under it, such as an email address or a token on screen.
colorNoText colour, a CSS colour such as #ffffff.
widthNoBox width, in percent of the annotation's box: the output frame for an arrow, the recording's picture for a blur. Not for text, whose box is its words.
endSecNo
heightNoBox height, in percent of the same box as width.
blurDataNoA blur's look: type blur or mosaic, shape rectangle or oval, color of the mosaic grid, intensity, blockSize.
fontSizeNoText size; 32 is the editor's default, a title reads well at 56 to 80.
startSecNo
animationNoHow the text enters: typewriter types it out, pop springs it in, and so on.
projectIdNoThe project to act on, from listProjects. Omit it only for the project open in the OpenScreen editor, which works only while the app runs.
backgroundNoColour of the plate behind the text, or "none" for no plate.
figureDataNoAn arrow's direction, colour and stroke width.
annotationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, which the description goes well beyond. It discloses partial-update semantics, type-conversion behavior (stays put on screen, default box for arrow/blur, text retained for revert), text-box refit around centre, rejection of cross-type arguments, and span-collision refusal with the conflicting annotation named.

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 long but front-loaded with verb+resource and ID, then proceeds field-group by field-group. Nearly every sentence carries distinct behavioral information (conversion rules, refit, refusals). It is dense rather than padded, though the enumerated field list is somewhat sprawling.

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?

For a 17-parameter mutation tool with nested objects and no output schema, the description covers the critical semantics: partial updates, type-conversion side effects, and input validation refusals. It does not describe what the call returns, but with no output schema that is not expected.

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 description coverage is 59%, so the description must compensate, and it does by grouping parameters semantically and flagging applicability (width/height only for arrow and blur, look fields only for text). It clarifies that figureData/blurData are partial (only passed keys change). Some nested fields like freehandPoints and endSec get no added meaning, but overall it adds substantial value over the 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?

States a specific verb (Change) on a specific resource (an existing annotation by id) and enumerates exactly which field groups are editable: span, type, centre, size, text/look, figureData/blurData. This clearly separates it from the sibling addAnnotation (creates) by specifying it mutates an existing annotation identified by id.

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?

Gives clear context: operate on an existing annotation by id, and only the fields passed are changed. It also documents refusal conditions (wrong-kind arguments, span collisions). However, it never explicitly names addAnnotation as the creation alternative or states when-not to use this tool, so routing guidance is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.