Reel-E

Property details

update_property_details

Destructive

Changes the listing's facts in Property details: price, bedrooms, bathrooms, square feet, listing status (active, coming soon, pending, sold), the listing description or the listing name (what the opening title shows when its wording is listing_name, for example 'Just Listed in Austin'; it is also the listing's own name in Reel-E, so the editor header, the listings list and download file names change with it). It updates the listing itself, the same as the Property details dialog, and the website and the opening title read it. On a listing whose website is live it needs the publish permission (Full control), since the site shows the change at once; without it nothing changes. It puts no text on the video; add_text and set_title do that. Suits 'change the price to 1.2 million', 'it's 4 beds' or 'mark it pending'. Uses no credit; undoable. Addresses are changed in Property details in Keylight. When a number could mean two things (for example 'six-bedroom bathroom count'), the person clarifies first.

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

Input Schema

Name	Required	Description
`beds`	No	Number of bedrooms; null clears it.
`sqft`	No	Interior square feet; null clears it.
`baths`	No	Whole or half baths, for example 2.5.
`price`	No	Listing price in dollars, for example 1200000.
`listingId`	Yes	Listing id from list_listings.
`description`	No	The new listing description, up to 4,000 characters.
`listingName`	No	The listing's name, shown by the opening title when its wording is listing_name. It is also the listing's own name in Reel-E (editor header, listings list, download file names).
`marketStatus`	No	Listing status: active, coming_soon, pending or sold.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 10, 2026
- addedInput schema / properties / beds / description
```
Added value: +"Number of bedrooms; null clears it."
```
- addedInput schema / properties / description / description
```
Added value: +"The new listing description, up to 4,000 characters."
```
- addedInput schema / properties / marketStatus / description
```
Added value: +"Listing status: active, coming_soon, pending or sold."
```
- addedInput schema / properties / sqft / description
```
Added value: +"Interior square feet; null clears it."
```
First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds material context beyond them: the publish permission (Full control) requirement on live-website listings with the consequence 'without it nothing changes', that the change propagates instantly to the website and opening title, that no credit is consumed, and that the operation is undoable. It also explains downstream effects (editor header, listings list, download file names change with the name) that no annotation conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single dense paragraph is front-loaded with the field list, which is good, but the listing_name parenthetical is long and largely duplicates the schema's own description of that parameter. The closing note about ambiguous numbers ('six-bedroom bathroom count') is confusingly worded relative to the point it makes, so some sentences do not fully earn their space.

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 an 8-parameter mutation tool with an output schema, this is complete: permissions, propagation timing, credit cost, reversibility, sibling alternatives, and out-of-scope fields (addresses) are all covered. Nothing an agent needs in order to call it correctly is missing.

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, but the description adds real meaning beyond it: it clarifies that listing_name is the listing's own name in Reel-E and therefore renames export files and headers, and it enumerates the four status values in prose alongside the enum. Its remaining value-add is modest because the schema descriptions already explain null-clearing and the 2.5-bath convention.

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?

States a specific verb ('Changes') and resource ('the listing's facts in Property details') and enumerates exactly which fields are covered: price, beds, baths, sqft, status, description, name. It explicitly separates itself from siblings that touch on-video text ('It puts no text on the video; add_text and set_title do that') and from address edits ('Addresses are changed in Property details in Keylight'), so an agent can route without opening a 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?

Gives concrete triggering utterances ('change the price to 1.2 million', "it's 4 beds", 'mark it pending'), names the alternatives for text (add_text, set_title), and states an exclusion (addresses handled elsewhere in Keylight). It even covers the ambiguity case ('When a number could mean two things... the person clarifies first'), which is explicit when-not-to-act guidance.

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?