Reel-E

Turn on MLS link

enable_mls_link

Destructive

Turns on the hosted MLS video link: a public, unbranded 16:9 page for MLS video fields. Needs the person's yes. get_mls_kit shows the kit first. On a Full control connection it starts at once; otherwise it returns a confirmationId and waits for the owner's yes.

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

Input Schema

Name	Required	Description	Default
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true, and non-idempotency; the description adds the crucial context that the result is a publicly visible page and that behavior forks by connection type — immediate on a Full control connection, otherwise it returns a confirmationId and blocks on owner approval. That dual-path, async-confirmation behavior is exactly the kind of thing annotations cannot express. It omits reversibility (whether/how the link can be taken down).

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?

Four short sentences, front-loaded with the effect and followed by prerequisite, then runtime behavior — a sensible order with no filler. Minor redundancy between 'Needs the person's yes' and 'waits for the owner's yes,' and terms like 'Full control connection' and 'confirmationId' are used without definition.

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 present, return values need no explanation, and the description covers effect, consent, prerequisite sibling, and the confirmation branch. The remaining gap is lifecycle: nothing says how to revoke the public link or what state the listing is left in if confirmation never arrives.

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?

Only one parameter (listingId) with 100% schema description coverage pointing to list_listings, so the schema carries the full burden. The description adds no additional meaning about the identifier, which is acceptable at this coverage level but earns no extra credit.

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 and resource ('Turns on the hosted MLS video link') and immediately defines what that resource is: 'a public, unbranded 16:9 page for MLS video fields.' This lets an agent distinguish it from the preview sibling get_mls_kit 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?

Explicitly names the prerequisite sibling ('get_mls_kit shows the kit first') and the consent gate ('Needs the person's yes'), which is real routing guidance. It stops short of stating when-not to use it (e.g., listing not ready, link already live), so it is strong but not exhaustive.

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?