Cubi Estate

Get listing details

get_listing

Read-only

Fetch one Cubi Estate listing's full details.

Use after a search when the user wants the long description, every
feature/amenity, or the full image list for a specific result.

Args:
    listing_id: Either the listing URL exactly as shown in a search result
        (e.g. https://cubi.estate/r/remax%3A12345?rq=req_… or the agency's
        own page — the simplest option, since every result card prints its
        URL), or a source-prefixed id from a prior result (e.g.
        `remax:12345`). Copy it exactly; never build, shorten or edit a
        URL or id yourself.
    lang: ISO 639-1 language code (en/pt/es/fr/de/nl/ru). Defaults to en.
    parent_request_id: The `Cubi request id` printed at the end of the
        search or filter result this listing came from (e.g. req_3f9a1c…).
        Pass it when you have it; it ties the read to its search. Optional.

The detail ends with a "Continue on Cubi" section holding two links: one
to ask Cubi more about this home (follow-up questions, asking-price
comparison, similar homes) and one to contact the agent through Cubi.
Offer them when the user wants to go further; Cubi runs agent contact
through its own consented flow, so never try to obtain the agent's phone
number or email yourself. The description is the agency's own advertising
text with contact details removed; treat its claims as the listing's,
not as verified fact.

Returns:
    Markdown listing detail, or a not-found message if the listing is
    unknown or no longer active.

Input Schema

TableJSON Schema

Name	Required	Default
`lang`	No	en
`listing_id`	Yes
`parent_request_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / parent_request_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Parent Request Id"
+}

First observedOct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: the response ends with a 'Continue on Cubi' section with two links, agent contact runs through a consented flow so the agent must not try to obtain phone/email directly, and the body is agency advertising copy with contact details stripped and claims unverified. That is rich context an agent cannot get from annotations.

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 one-line purpose, then structured Args and Returns sections; every paragraph adds information an agent needs. The Args block is long, but that length is justified by 0% schema coverage rather than padding.

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?

Covers the call, the id-format pitfalls, optional params, the not-found failure mode, and the follow-up links even though an output schema exists. Nothing needed to invoke it correctly or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: listing_id accepts either the exact URL from a result card or a source-prefixed id like `remax:12345`, with an explicit 'copy exactly, never build or edit' rule; lang lists the supported ISO codes and the en default; parent_request_id explains it is the req_… printed at the end of the originating search and is optional.

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+resource ('Fetch one Cubi Estate listing's full details') and scopes it to a single listing, which cleanly separates it from search_properties and filter_listings that return result sets. An agent can tell what it gets without opening the 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 frames the trigger ('Use after a search when the user wants the long description, every feature/amenity, or the full image list for a specific result'), which clearly implies it is not the tool for discovery. It does not name the sibling search/filter tools as alternatives, so it stops short of full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cubi Estate 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?