AskEditor

Add text layer

add_text

[write] Add a text layer (title, headline, lower third, label) on its own top lane; style fields override the preset. items places every word of a sheet in one save. Use for on-screen words that are not spoken captions. Not for captions (use add_caption_line or import_captions) or changing existing text (use set_text). Returns the changed clips' rows (with handles) and counts. The new layer's handle is in changed. Related: set_text, set_clip_animation, align_clip.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "add_text"
  }
}

Input Schema

Name	Required	Description
`x`	No	Frame-width % from centre (+ right).
`y`	No	Frame-height % from centre (+ down).
`bg`	No	Box behind, #rrggbb (default none).
`font`	No	Font family (default Poppins).
`size`	No	px at 1080p, 8–400 (default 72).
`text`	No	The words (required).
`align`	No	Line alignment (default center).
`color`	No	#rrggbb (default #ffffff).
`items`	No	Several layers; each takes the fields above.
`italic`	No	Italic.
`preset`	No	Seeds style and placement.
`shadow`	No	Softness, px at 1080p, 0–60.
`stroke`	No	Outline, px at 1080p, 0–20.
`weight`	No	100–900 (default 700).
`shadowX`	No	Offset, px at 1080p, -60–60; with shadow 0, a hard shadow.
`shadowY`	No	As shadowX, + = down.
`startMs`	No	Start, ms (default 0).
`fitWidth`	No	Fill this % of frame width (10–100) on one line; overrides size.
`maxWidth`	No	Wrap width, % of frame, 20–100 (default 80).
`bgOpacity`	No	Box opacity, 0–1 (default 1).
`uppercase`	No	All caps.
`durationMs`	No	Length, ms (default 3000).
`lineHeight`	No	× size, 0.7–2.5 (default 1.15).
`project_id`	Yes	The AskEditor project this acts on (from list_projects).
`strokeColor`	No	Outline colour, #rrggbb (default #000000).
`letterSpacing`	No	em, -0.1–0.5 (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare write semantics (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the mutation profile is covered. The description adds genuinely useful behavior beyond that: the batch mode ('items places every word of a sheet in one save'), the return payload (changed clips' rows with handles and counts), and where the new handle lives (changed). It stops short of noting that repeated calls are not idempotent (annotations flag this) or any project-state prerequisites, so it adds context but not a rich behavioral picture.

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 dense sentences: purpose first, then usage/exclusions, then return shape and related tools. No filler, and the most decision-relevant content (what it makes, what it replaces) is front-loaded.

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

Completeness5/5

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

For a 26-parameter write tool with no output schema and no nested objects, the description covers everything an agent would otherwise have to guess: batch mode via `items`, preset-vs-field precedence, return payload and handle location, and where to go for adjacent tasks. Combined with 100% schema coverage and annotations, nothing material is missing.

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%, so the schema already documents all 26 parameters including ranges, defaults and enums. The description contributes two real semantic rules that the schema cannot express: 'style fields override the preset' and that `items` batches many layers in one save. Beyond those, it adds no syntax or format detail over the schema, so baseline 3 plus those two rules is right.

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?

Opens with a specific verb+resource ('Add a text layer') and immediately scopes the variants it covers (title, headline, lower third, label) plus the placement rule ('own top lane'). It explicitly names the sibling tools it is not (add_caption_line, import_captions, set_text), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Gives a positive use condition ('on-screen words that are not spoken captions') and two explicit exclusions that route to named alternatives: captions go to add_caption_line/import_captions, editing existing text goes to set_text. This is the when/when-not/alternatives pattern at full strength.

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

All AskEditor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?