Market and Regulatory Data Feeds — Zinin M2M Hub

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

Name	Required	Description	Default
`city`	No	Emlakjet.com location slug. "istanbul" for the whole city, or an Istanbul district like "istanbul-kadikoy".	istanbul
`deal_type`	Yes	Sale (satilik) or rent (kiralik) listings.	satilik
`max_items`	No	Maximum number of listing rows to return in this run.
`max_pages`	No	How 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_type`	Yes	daire (apartment) or konut (residential/housing — a broader Emlakjet category that overlaps with, but is not identical to, daire).	daire

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds value beyond this by noting 'No login, no browser, no proxies' and mentioning the $0.02/call cost. This provides auth and operational context not present in annotations.

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?

The description is a concise two-sentence summary, front-loaded with the core action and resource. Every clause adds value: live data, source, scope, access method, and cost. No unnecessary repetition.

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?

Given the rich schema (5 params, full descriptions), read-only annotations, and clear description of source/scope/access, the tool is fully specified for selection and invocation. No output schema exists, but the purpose of returning listings is unambiguous.

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?

Input schema covers 100% of parameters with detailed descriptions. The tool description only echoes 'by deal type (sale/rent) and property type,' adding no new meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 tool pulls live apartment/housing listings from Emlakjet.com for Istanbul, naming the specific portal and city. It distinguishes from sibling real-estate tools, which target other portals/cities.

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 gives clear context for when to use it (Istanbul listings from Emlakjet, no login/browser/proxies) but does not explicitly mention when not to use it or name alternatives. It implies the appropriate use case without exclusion guidance.

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

All Market and Regulatory Data Feeds — Zinin M2M Hub tools Inspect

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

Disambiguation2/5

Many tools have overlapping purposes, with over a dozen real-estate scrapers and half a dozen job boards differentiated only by geography. While descriptions are clear, an agent would struggle to pick the correct tool without prior knowledge of the specific site or region, leading to frequent misselection.

Naming Consistency2/5

Tool names use a mix of lowercase-hyphenated (boss-az, clinical-trials-monitor), underscore (pricing_info), and long descriptive phrases (official-gazette-regulatory-action-router). No consistent verb_noun pattern exists; some start with source domains, others with action nouns. This lack of predictability makes navigation confusing.

Tool Count3/5

36 tools is on the heavy side for a server that could have been more focused. While a 'data hub' can justify many endpoints, the high number of near-identical scrapers (12+ real estate, 6+ job boards) suggests bloat rather than well-scoped functionality. A leaner set with parameterized regional filters would be more appropriate.

Completeness2/5

The claimed domain 'Market and Regulatory Data Feeds' is poorly served: there are no stock/forex/commodity price feeds, few global regulatory sources (only FDA, SEC, EU tenders), and many tools are for job and property listings which are tangential. The set feels like a random aggregation rather than a coherent surface, with obvious gaps for core market and regulatory data.

Resources

Need Help?