Reel-E

Edit text

update_text

Destructive

Change an existing text overlay (textId from the edit summary).

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": {
      "listingId": "<listingId>",
      "textId": "<textId>"
    },
    "name": "update_text"
  }
}

Input Schema

Name	Required	Description
`size`	No	Text size: small, medium or large.
`text`	No	The words to show, up to 120 characters.
`color`	No	Text color as a hex code, like #FFFFFF.
`fontId`	No	Font: dm-sans, tenor-sans, montserrat, space-grotesk or ibm-plex-mono.
`textId`	Yes	The text overlay to change: its textId from the edit summary.
`animation`	No	How it comes on: none, fade, pop or slide-up.
`listingId`	Yes	Listing id from list_listings.
`placement`	No	Where it sits on screen: top, center or lower.
`endSeconds`	No	When the text disappears, in seconds; at least 1 s after startSeconds.
`startSeconds`	No	When the text appears, in seconds from the start (0.1 s steps).

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 10, 2026

addedInput schema / properties / animation / description

Added value: +"How it comes on: none, fade, pop or slide-up."

addedInput schema / properties / color / description

Added value: +"Text color as a hex code, like #FFFFFF."

addedInput schema / properties / endSeconds / description

Added value: +"When the text disappears, in seconds; at least 1 s after startSeconds."

addedInput schema / properties / fontId / description

Added value: +"Font: dm-sans, tenor-sans, montserrat, space-grotesk or ibm-plex-mono."

addedInput schema / properties / placement / description

Added value: +"Where it sits on screen: top, center or lower."

addedInput schema / properties / size / description

Added value: +"Text size: small, medium or large."

addedInput schema / properties / startSeconds / description

Added value: +"When the text appears, in seconds from the start (0.1 s steps)."

addedInput schema / properties / text / description

Added value: +"The words to show, up to 120 characters."

addedInput schema / properties / textId / description

Added value: +"The text overlay to change: its textId from the edit summary."

First observedNov 9, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the description should clarify what makes it destructive. Instead it says nothing about whether omitted fields are reset, whether it is a partial patch or a full replace, or that start/end timing constraints are validated — all critical for a destructive, non-idempotent mutation.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the brevity is achieved by omitting information rather than by tight editing of a complete statement.

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

Completeness2/5

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

For a destructive, non-idempotent mutation with 10 parameters, the description covers only the identifier source. An output schema exists so return values need no explanation, but update semantics (partial vs full, resets of unspecified fields, timing validation) remain unaddressed.

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% with enums and per-field descriptions for all 10 parameters, so the schema carries the semantics. The description adds only a restatement of textId's origin, which is already in the schema's own description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Change an existing text overlay'. That cleanly separates it from add_text/remove_text by implication (existing vs new vs deleted), though it never names those siblings explicitly. An agent knows what it does but must infer the distinction.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it says the tool targets an existing overlay and that textId comes 'from the edit summary', which hints at a prerequisite call to get_edit_summary. There is no explicit when-to-use/when-not guidance and no pointer to add_text for creating overlays.

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

All Reel-E 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?