Reel-E

Add sticker

add_sticker

Destructive

Add a badge like "Just listed" or "Open house". open_house, price_reduced and a few others take one short line (e.g. "Sat 1-4 PM").

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>",
      "kind": "<kind>"
    },
    "name": "add_sticker"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Which badge, like just_listed, open_house or price_reduced.
`line`	No	One short line under the badge, like 'Sat 1-4 PM', up to 32 characters.
`design`	No	The badge's look; default classic.
`listingId`	Yes	Listing id from list_listings.
`endSeconds`	No	When the badge disappears, in seconds; default 4 s after it appears.
`wholeVideo`	No	true shows the badge for the whole video; default is a time range.
`startSeconds`	No	When the badge appears, in seconds; default 0.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026

addedInput schema / properties / design / description

Added value: +"The badge's look; default classic."

addedInput schema / properties / endSeconds / description

Added value: +"When the badge disappears, in seconds; default 4 s after it appears."

addedInput schema / properties / kind / description

Added value: +"Which badge, like just_listed, open_house or price_reduced."

addedInput schema / properties / line / description

Added value: +"One short line under the badge, like 'Sat 1-4 PM', up to 32 characters."

addedInput schema / properties / startSeconds / description

Added value: +"When the badge appears, in seconds; default 0."

addedInput schema / properties / wholeVideo / description

Added value: +"true shows the badge for the whole video; default is a time range."

First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, destructive mutation, so the description need not restate safety basics. It adds that some badge kinds require a short line, but it does not clarify what the destructive hint means for the video, whether multiple stickers can coexist, or what permissions are needed.

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?

Two compact sentences, front-loaded with purpose and followed by a targeted constraint about line text. No redundant restatement of the title or schema fields.

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?

With an output schema and full parameter descriptions, the definition does not need to explain return values or each field. It remains slightly incomplete on when to choose this over sibling tools and on the practical meaning of the destructive annotation, but it is sufficient for correct invocation.

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 100%, so parameters are already documented. The description still adds useful semantic guidance by naming badge kinds (open_house, price_reduced) that typically use the short line field, which goes beyond the schema's generic line 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 ('Add a badge') and gives concrete badge examples, so an agent can identify the operation immediately. It does not explicitly distinguish itself from the sibling remove_sticker, which keeps it below the top score.

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?

It offers examples of badges but no explicit when-to-use/when-not-to-use guidance, prerequisites, or alternative tools. An agent must infer that this is the tool for adding a badge rather than removing or replacing one.

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?