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://www.example.com/property/123 — the simplest option,
        since every result card prints its URL), or a source-prefixed id
        from a prior result (e.g. `remax:12345`). Do not invent either.
    lang: ISO 639-1 language code (en/pt/es/fr/de/nl/ru). Defaults to en.

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	Description	Default
`lang`	No		en
`listing_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, non-destructive, closed-world), while the description adds substantial behavioral context the schema cannot convey: the detail ends with a two-link 'Continue on Cubi' section, contact runs through a consented in-app flow, and the description text is unverified agency advertising with contacts stripped, plus a not-found outcome.

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 purpose before the Args block, and every sentence carries actionable content. The 'Returns:' section is somewhat redundant given an output schema exists, which keeps it from a 5.

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 two-parameter read tool with annotations covering safety and an existing output schema, the description still supplies everything an agent needs: call triggers, both parameter formats, the returned section structure, contact-flow constraints, and failure behavior.

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 must carry the parameters, and it does: listing_id accepts either an exact result-card URL or a source-prefixed id like `remax:12345` (with an explicit 'do not invent' warning), and lang is an ISO 639-1 code with a listed enum-like set and default of en.

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 ('Fetch') and resource ('one Cubi Estate listing's full details'), and explicitly frames it as the detail-retrieval companion to search ('Use after a search'), which cleanly separates it from siblings search_properties and filter_listings.

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 an explicit trigger condition (after a search, when the user wants the long description, all amenities, or the full image list), plus concrete workflow guidance on when to offer the 'Continue on Cubi' links and a hard prohibition against trying to obtain agent contact details.

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?