AskEditor

Edit text layer

set_text

Destructive

[write] Change a text clip's words and/or style. preset replaces the style first; passed fields merge over it. ids restyles several at once. Use to fix wording or restyle titles. Not for caption lines (use edit_subtitle_line), the caption style (use set_subtitle_style) or placement (use set_clip_transform). Returns the changed clips' rows (with handles) and counts. Related: add_text, set_clip_transform, set_clip_animation.

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": "set_text"
  }
}

Input Schema

Name	Required	Description
`bg`	No	Box behind, #rrggbb.
`id`	No	get_timeline handle.
`ids`	No	More handles.
`font`	No	Font family.
`size`	No	px at 1080p, 8–400.
`text`	No	New words.
`align`	No	Line alignment.
`color`	No	#rrggbb.
`items`	No	Many clips at once, max 60, each with this tool's fields.
`italic`	No	Italic.
`preset`	No	Base style.
`shadow`	No	Softness, px at 1080p, 0–60.
`stroke`	No	Outline, px at 1080p, 0–20.
`weight`	No	100–900.
`shadowX`	No	Offset, px at 1080p, -60–60; with shadow 0, a hard shadow.
`shadowY`	No	As shadowX, + = down.
`fitWidth`	No	Fill this % of frame width (10–100) on one line; overrides size.
`maxWidth`	No	Wrap width, % of frame, 20–100.
`bgOpacity`	No	Box opacity, 0–1.
`uppercase`	No	All caps.
`lineHeight`	No	× size, 0.7–2.5.
`project_id`	Yes	The AskEditor project this acts on (from list_projects).
`strokeColor`	No	Outline colour, #rrggbb.
`letterSpacing`	No	em, -0.1–0.5.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so the safety bar is lower. The description still adds real behavior: preset replaces the style first and passed fields merge over it, and it discloses the return shape (changed rows with handles plus counts). It doesn't spell out what a preset swap discards or whether style fields are lost when omitted, which keeps it below a 5.

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?

Four tight sentences, front-loaded with the write action and merge rule, then usage exclusions, then return value. The trailing "Related:" list is short and useful; nothing is redundant with the schema.

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 24-parameter destructive mutation with no output schema, the description still covers purpose, merge semantics, batch behavior, return value, and sibling routing. An agent has everything needed to decide and invoke correctly.

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 coverage is 100%, so the baseline is 3; the description earns extra credit by explaining the interaction between `preset` and the individual style fields (replace-then-merge) and the difference between `id` and `ids`. That merge-precedence rule is not derivable from the schema alone.

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?

Specific verb+resource: "Change a text clip's words and/or style", with the [write] tag flagging the operation class. It also explains batch scope ("ids restyles several at once") and the preset-over-merge ordering, so the agent knows exactly what the call mutates without opening the 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?

Explicit when-to-use ("Use to fix wording or restyle titles") and three explicit when-not-to-use cases with named alternatives: caption lines → edit_subtitle_line, caption style → set_subtitle_style, placement → set_clip_transform. This is textbook routing guidance.

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?