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.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_listing"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	ISO 639-1 language code (en/pt/es/fr/de/nl/ru). Defaults to en.	en
`listing_id`	Yes	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.
`parent_request_id`	No	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.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 11, 2026

addedInput schema / properties / lang / description

Added value: +"ISO 639-1 language code (en/pt/es/fr/de/nl/ru). Defaults to en."

addedInput schema / properties / listing_id / description

Added value: +"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."

addedInput schema / properties / parent_request_id / description

Added value: +"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."

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.4/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations it discloses genuinely useful behavior: the result ends in a 'Continue on Cubi' section with two links, agent contact runs through a consented flow so the model must never try to extract phone/email, and the ad text has contact details stripped and should be treated as the listing's claims, not verified fact. It also states the failure mode (not-found message for unknown or inactive listings), which annotations alone would not reveal.

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?

Purpose and usage are front-loaded in the first two sentences, and the trust/contact caveats are placed where they matter. The Args section duplicates schema text word-for-word and is the one block that does not earn its place in the description.

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 a single-record read with a rich input schema and an output schema, the description covers everything an agent needs: exact-id copy rules, optional request-id linkage, the shape of the returned markdown, and the trust caveat about advertising copy. Return formatting is already handled by the output schema, so nothing material is missing.

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?

Schema coverage is 100%, so the baseline is 3, and the Args block reproduces the schema descriptions essentially verbatim ('copy it exactly; never build, shorten or edit') rather than extending them. The 'ties the read to its search' rationale for parent_request_id is already in the schema, so no meaning is added beyond structured data.

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 ('Fetch one Cubi Estate listing's full details') and immediately scopes it as a detail-fetch that follows a search, which separates it from search_properties and filter_listings. The three named reasons to call it (long description, features/amenities, full image list) make the resource boundary concrete.

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?

'Use after a search when the user wants the long description, every feature/amenity, or the full image list for a specific result' gives a clear trigger condition rather than leaving usage implied. It also routes downstream intent ('offer them when the user wants to go further'), but it does not state when NOT to call it or name an alternative detail source among the siblings.

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?