Reel-E

Add text

add_text

Destructive

Add a text overlay for a time range (seconds, 0.1s steps, at least 1s). At most 8.

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>",
      "text": "<text>",
      "startSeconds": "<startSeconds>",
      "endSeconds": "<endSeconds>"
    },
    "name": "add_text"
  }
}

Input Schema

Name	Required	Description
`size`	No	Text size: small, medium or large.
`text`	Yes	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.
`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`	Yes	When the text disappears, in seconds; at least 1 s after startSeconds.
`startSeconds`	Yes	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.

Changed8 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."

First observedNov 9, 2026

TDQS

B3.2/5.0

Behavior3/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 mutation risk profile is covered structurally. The description adds genuine behavioral context beyond that: the 0.1s step granularity, the minimum 1s duration, and a hard cap of 8 overlays. It does not say what happens when the cap is exceeded or what the call returns, so it stops at adequate.

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?

Two short sentences with the resource and its constraints front-loaded and no filler. 'At most 8.' is terse to the point of being cryptic about what the limit applies to, which costs it a point but not more.

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

Completeness3/5

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

With an output schema present the return values need no explanation, and the schema covers all nine parameters. What is missing for a destructive mutation with nine parameters is the effect of exceeding the eight-overlay limit, whether the listing must be in a draft, and how this relates to the sibling edit tools.

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 description coverage is 100% and four parameters are enums, so the schema already documents size, color, fontId, animation, placement, text and the seconds fields in detail. The description's timing constraints largely restate the endSeconds description ('at least 1 s after startSeconds') and the 0.1s step already stated for startSeconds, adding little new meaning.

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 ('Add a text overlay') and bounds it by a time range in seconds, so an agent can tell this creates a timed text element rather than editing one. It does not explicitly contrast with remove_text or update_text, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus update_text (to change an existing overlay) or remove_text (to delete one), and no prerequisites such as the listing needing to be in an editable state. The only usage-adjacent guidance is the implicit 'At most 8' cap, which is a limit rather than a routing rule.

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?