Skip to main content
Glama

Market Data

by com.timzinin.api

Emlakjet Istanbul Real Estate Listings

emlakjet-istanbul
Read-only

Pull live apartment/housing listings straight from Emlakjet.com for Istanbul — one of Turkey's biggest real-estate classifieds portals — by deal type (sale/rent) and property type. No login, no browser, no proxies. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoEmlakjet.com location slug. "istanbul" for the whole city, or an Istanbul district like "istanbul-kadikoy".istanbul
deal_typeYesSale (satilik) or rent (kiralik) listings.satilik
max_itemsNoMaximum number of listing rows to return in this run.
max_pagesNoHow many result pages to walk before stopping. Emlakjet.com itself caps browsable depth at 50 pages per search (verified live), regardless of total inventory.
property_typeYesdaire (apartment) or konut (residential/housing — a broader Emlakjet category that overlaps with, but is not identical to, daire).daire

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so no extra safety signal is needed. The description adds useful behavioral details: 'No login, no browser, no proxies' and a per-call cost, which goes beyond the 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?

The description is concise and front-loaded with the main action, but includes a marketing phrase ('one of Turkey's biggest real-estate classifieds portals') that doesn't carry functional value. Overall it's efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, and the description does not explain what fields the returned listings will contain or how pagination works. It covers the essential use case but leaves a clear gap in expected output structure.

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 description coverage is 100%, with each parameter fully documented in the input schema. The description only mentions deal type and property type at a high level, adding no extra semantic value beyond the schema.

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?

The description clearly states the verb 'Pull', the resource 'Emlakjet.com', and the scope 'Istanbul', with a specific focus on deal type and property type. It distinguishes itself from siblings by its geographic and source specificity.

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 description implies use when the user needs live apartment/housing listings from Istanbul, with no login or browser required. It doesn't explicitly name alternative tools, but the Istanbul focus and portal name provide clear context for when to use this tool.

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

All Market Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

Many tools are distinct by region/source (e.g., otodom-warsaw vs. imovirtual-lisbon), but there are overlapping categories: multiple real estate, job, SEC, and crypto tools. Watchers/alerts (job-alert, re-new-listing-alert, tender-alert) could be confused with their corresponding search tools, and token tools (live-price-oracle, token-launch-radar, rug-pull-scorer) have similar purposes.

Naming Consistency2/5

Names follow no consistent pattern: some are hyphenated source-location (emlakjet-istanbul), some are generic descriptors (job-alert, pricing_info uses underscore), and some are verbose phrases (official-gazette-regulatory-action-router). There is no consistent verb_noun or noun structure, making it hard to predict what a tool does from its name.

Tool Count2/5

With 36 tools, the server is in the 'too many' range (25+). The broad 'Market Data' theme partially justifies the count, but it feels bloated with many single-country listings and overlapping watchers that could be consolidated.

Completeness3/5

The domain is loosely defined as 'market data,' spanning real estate, jobs, tenders, SEC filings, crypto, and clinical trials. While it covers niche areas well, there are notable gaps: no general stock/ETF quotes, no forex/commodities data, and no cross-country aggregate search. The mix of scrapers and alerts leaves the surface feeling uneven.

Resources