Reel-E

Opening title

set_title

Destructive

The opening title card over the first shots: whether it shows, its DESIGN (the same designs as the Text panel's design buttons; browse_options title_designs shows what each looks like), WHICH WORDS it shows (the address, or the listing name, like the Text panel's Address / Listing name switch), which listing facts it shows (price, bedrooms, bathrooms, square feet) and its background. The words come from Property details, as in the Studio: for a title like 'Just Listed in Austin', update_property_details sets the listing name and wording listing_name here shows it. The address itself is changed in Property details. The result says exactly what visibly changed, or why nothing did.

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

Input Schema

Name	Required	Description
`show`	No	Facts to show (true) or hide (false). Omitted facts stay as they are.
`design`	No	Design id. browse_options title_designs gives each design's name and what it looks like.
`enabled`	No	Show (true) or hide (false) the opening title.
`wording`	No	Show the street address, or the listing name from Property details.
`listingId`	Yes	Listing id from list_listings.
`background`	No	Glass (frosted) or plain background, or none. Only designs with a background.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 10, 2026
- addedInput schema / properties / enabled / description
```
Added value: +"Show (true) or hide (false) the opening title."
```
- addedInput schema / properties / show / properties / baths / description
```
Added value: +"Show the bathroom count on the title."
```
- addedInput schema / properties / show / properties / beds / description
```
Added value: +"Show the bedroom count on the title."
```
- addedInput schema / properties / show / properties / price / description
```
Added value: +"Show the price on the title."
```
- addedInput schema / properties / show / properties / sqft / description
```
Added value: +"Show the square feet on the title."
```

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / design / description

Previous value: -"Design id. ed-gallery = Gallery; ed-caption = Caption; ed-signature = Signature; lux-maison = Maison; lux-atelier = Atelier; lux-estate = Estate; lux-noir = Noir; bold-headline = Headline; bold-label = Label; bold-poster = Poster; arch-plan = Plan; arch-elevation = Elevation; soft-hearth = Hearth; soft-porch = Porch; coast-shoreline = Shoreline; coast-tide = Tide; urban-metro = Metro; urban-avenue = Avenue; x-monument = Monument; x-ticket = Ticket; x-index = Index; x-marquee = Marquee; x-script = Script; x-columns = Columns; x-spine = Spine; x-outline = Outline; x-split = Split; x-underline = Underline; tracking-card = Tracking Card; panel-pill-bar = Pill Bar; hybrid-spec-pill-sans = Spec Pill Sans; minimal-hairline = Hairline; hybrid-icon-pill-serif = Icon Pill Serif; panel-lower-third = Lower Third; minimal-serif-blur = Serif Blur; hybrid-icon-pill-grotesk = Icon Pill Grotesk; panel-serif-editorial = Serif Editorial; panel-cinematic-band = Cinematic Band; panel-compact-card = Compact Card; panel-icon-grid = Icon Grid."New value: +"Design id. browse_options title_designs gives each design's name and what it looks like."

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations declare destructiveHint=true and idempotentHint=false, yet the description portrays a benign settings setter with no mention of what existing title configuration gets overwritten or why repeated identical calls might not be idempotent. It does add genuine behavioral context beyond annotations by explaining data provenance (words come from Property details, 'as in the Studio') and that the result reports exactly what visibly changed or why nothing did.

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?

Front-loads the object of the operation and then walks through each controllable aspect, with no filler sentences. It is dense and slightly run-on in the design clause, but each clause carries distinct information about a different parameter.

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?

Covers all six parameters, their provenance, and the reporting behavior, which is sufficient for a configuration tool with a full schema and an output schema. The one meaningful omission is any warning about the destructive/non-idempotent traits the annotations advertise.

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 baseline is 3, but the description adds real meaning: design ids map to the Text panel's design buttons with browse_options as the lookup, and wording maps to the Address / Listing name switch with the listing name sourced from update_property_details. The note that background applies only to designs that have one clarifies an enum constraint the schema does not state.

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?

Identifies the exact object being manipulated (the opening title card over the first shots) and enumerates every facet it controls: visibility, design, wording source, shown facts, and background. It also draws an explicit boundary against a sibling by stating that the address itself is changed in Property details, so an agent can separate this from update_property_details without opening either schema.

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

Usage Guidelines4/5

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

Gives clear usage context and routes two related tasks elsewhere: design previews to browse_options title_designs, and address/listing-name text to update_property_details. It never explicitly excludes alternatives like add_text or set_captions for on-screen text, so an agent must still infer that this tool is specifically for the opening title rather than any overlay.

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?