Skip to main content
Glama

Objelio Immobiliensuche

Get listing details

get_listing
Read-onlyIdempotent

Use this when the user asks about one listing from search_listings or compare_listings. Full published details of one listing: description, features, energy certificate, commission (Courtage), the offering agent and the link to the listing page.

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

NameRequiredDescriptionDefault
search_idNoThe suche_id from search_listings, so an inquiry can be linked to the search.
listing_idYesThe id from search_listings.

Output Schema

NameRequiredDescriptionDefault
idYes
ortYes
plzYes
demoYes
lageYes
linkYesListing page on objelio.de, where the user contacts the agent.
titelYes
bilderNoURLs of up to 8 photos in the agent's order; the first is titelbild.
angebotYes
hinweisYes
anbieterYesThe offering agent.
courtageYesBuyer's commission.
merkmaleYesFeatures: true, false or null (no information).
ortsteilYes
umgebungNoNearest school, kindergarten, station, bus stop, supermarket and pharmacy (null = not determined yet).
objektartYes
preis_eurYes
titelbildYes
ausstattungYes
anfrage_linkYesOpens the contact form for the agent on the listing page. Offer it when the user is interested, e.g. wants to visit or ask a question. null for demo listings.
beschreibungYes
demo_hinweisNo
bestaetigt_amYesWhen the agent last confirmed that the listing and its details are current.
energieausweisYes
haeufige_fragenNoQuestions and answers in German, built only from the stored data; the same as on the listing page. Costs and rate are estimates.
preis_auf_anfrageYestrue = the agent does not publish the price (price on request); preis_eur is then null; no price is known.
veroeffentlicht_amYesWhen the listing was published on Objelio (start of the current publication).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / link / description
      Previous value: -"Listing page on objelio.de, where the user contacts the agent. Always show it."New value: +"Listing page on objelio.de, where the user contacts the agent."
    • changedOutput schema / properties / preis_auf_anfrage / description
      Previous value: -"true = the agent does not publish the price (price on request); preis_eur is then null. Say so and never estimate a price."New value: +"true = the agent does not publish the price (price on request); preis_eur is then null; no price is known."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / anfrage_link
      Added value: +{
      +  "description": "Opens the contact form for the agent on the listing page. Offer it when the user is interested, e.g. wants to visit or ask a question. null for demo listings.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "link",
      -  "demo",
      -  "titel",
      -  "objektart",
      -  "angebot",
      -  "lage",
      -  "plz",
      -  "ort",
      -  "ortsteil",
      -  "preis_eur",
      -  "preis_auf_anfrage",
      -  "merkmale",
      -  "beschreibung",
      -  "ausstattung",
      -  "energieausweis",
      -  "courtage",
      -  "anbieter",
      -  "titelbild",
      -  "veroeffentlicht_am",
      -  "bestaetigt_am",
      -  "hinweis"
      -]New value: +[
      +  "id",
      +  "link",
      +  "anfrage_link",
      +  "demo",
      +  "titel",
      +  "objektart",
      +  "angebot",
      +  "lage",
      +  "plz",
      +  "ort",
      +  "ortsteil",
      +  "preis_eur",
      +  "preis_auf_anfrage",
      +  "merkmale",
      +  "beschreibung",
      +  "ausstattung",
      +  "energieausweis",
      +  "courtage",
      +  "anbieter",
      +  "titelbild",
      +  "veroeffentlicht_am",
      +  "bestaetigt_am",
      +  "hinweis"
      +]
  3. Changed10 schema fields changed
    • addedOutput schema / properties / merkmale / properties / Einliegerwohnung
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Fußbodenheizung
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Glasfaser
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Kamin
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Klimaanlage
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Photovoltaik
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Sauna
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Wallbox
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Wintergarten
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / merkmale / properties / Wärmepumpe
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / merkmale / properties / Pool
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  5. Changed1 schema field changed
    • addedOutput schema / properties / veroeffentlicht_am / description
      Added value: +"When the listing was published on Objelio (start of the current publication)."
  6. Changed2 schema fields changed
    • addedOutput schema / properties / haeufige_fragen
      Added value: +{
      +  "description": "Questions and answers in German, built only from the stored data; the same as on the listing page. Costs and rate are estimates.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "antwort": {
      +        "type": "string"
      +      },
      +      "frage": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "frage",
      +      "antwort"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / umgebung
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "orte": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "art": {
      +                "description": "Kind of place in German, e.g. Schule, Kita, Supermarkt.",
      +                "type": "string"
      +              },
      +              "entfernung": {
      +                "description": "Rounded straight-line distance in German, e.g. \"ca. 350 m\". Not a walking or driving distance.",
      +                "type": "string"
      +              },
      +              "name": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              }
      +            },
      +            "required": [
      +              "art",
      +              "name",
      +              "entfernung"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "quelle": {
      +          "description": "Data source (OpenStreetMap). Mention it when you use the distances.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "orte",
      +        "quelle"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Nearest school, kindergarten, station, bus stop, supermarket and pharmacy (null = not determined yet)."
      +}
  7. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it returns only 'published' details, signaling that unpublished or draft listings may not be retrievable, and it previews the returned content areas. It does not cover error cases or permissions.

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

Conciseness5/5

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

Two sentences with no filler. The use-case trigger is front-loaded and the payload enumeration follows immediately, so an agent gets both routing and expectation-setting at a glance.

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?

With an output schema present, return-value structure need not be explained, and rich annotations cover safety and idempotency. The description still adds the 'published' qualifier and the source-of-id routing, leaving nothing an agent needs to call this correctly.

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% and both parameters (listing_id, search_id) are already documented in the schema, including their origin in search_listings. The description references search_listings/compare_listings as the source of a listing, but adds no new syntax or constraint detail beyond what the schema provides, so baseline 3 applies.

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 (get) and resource (one listing) and enumerates the payload: description, features, energy certificate, commission (Courtage), offering agent, listing link. That enumeration distinguishes it sharply from search_listings and compare_listings, which the description also names.

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?

Gives an explicit trigger condition ('when the user asks about one listing from search_listings or compare_listings'), which routes the agent from the list/compare results to this detail tool. It lacks an explicit when-not or negative condition, but the positive routing is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources