Skip to main content
Glama

emlakjet_listing_detail

Retrieves complete details for a real-estate listing by its URL or numeric ID, including price, address, rooms, area, specifications, and images.

Instructions

Full detail of one listing: title, price (TRY), description, address (neighbourhood/district/city), rooms count, area in m², 14 spec fields (heating, parking, title deed, elevator, balcony, usage, loan eligibility…), images. url_or_id: the listing URL from emlakjet_search, or its numeric id.

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": {
      "url_or_id": "<url_or_id>"
    },
    "name": "emlakjet_listing_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_or_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It thoroughly discloses the shape of the returned data (TRY pricing, address granularity, 14 spec fields, images), but says nothing about failure modes for invalid ids, rate limits, auth, or whether it is a pure read. Adequate but incomplete for an unannotated tool.

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?

A single dense sentence plus a short parameter note, front-loaded with the highest-value fact (what is returned) before the argument clarification. Minor waste: listing the individual fields is partly redundant since an output schema exists.

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?

One required parameter, an output schema present, and the description covers both the source of the input value and the shape of the return. It is essentially complete for a straightforward single-listing fetch, with only error/edge-case behavior left unspecified.

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

Parameters4/5

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

Schema description coverage is 0% – the schema only names 'url_or_id' as a string. The description compensates by stating it accepts either a listing URL obtained from emlakjet_search or a numeric id, which is meaningful guidance the schema does not provide. It omits id format details or what happens if an id is stale, so not a 5.

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 ('Full detail of one listing') and enumerates what detail means: title, price in TRY, description, address hierarchy, rooms, area, spec fields, images. This distinguishes it clearly from emlakjet_search, which the description references by name.

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?

The parameter note 'the listing URL from emlakjet_search' implicitly tells the agent this is a follow-up call after search, which is a clear usage context. It stops short of an explicit when-not clause or mentioning the other siblings (price_stats, list_districts) as alternatives.

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