Skip to main content
Glama
shojaee76-cmyk

divar-mcp

by shojaee76-cmyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

divar_search

Search live Divar.ir ads using text query, city, category, price, photo, district, or brand filters. Retrieve normalized rows with title, price, city, district, and image.

Instructions

Search live divar.ir listings (Iran's largest classifieds). Read-only, no account needed. Supports text query, city, category, Toman price range, photo-only, district ids and brand/model, with cursor pagination. Returns normalized rows (token, title, price in Toman, city, district, relative time, image, url).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity id (e.g. "1") or Persian name (e.g. "تهران").
sortNoClient-side sort of the sampled rows.
limitNoReturn at most this many rows.
pagesNoCursor pages to fetch (1-5, default 1).
queryNoFree-text search, Persian (e.g. "پژو ۲۰۶").
categoryNoDivar category slug, e.g. mobile-phones, light, buy-residential. See divar_list_categories.
has_photoNoOnly posts with photos.
page_sizeNoRows per page (max 60, default 24).
price_maxNoPrice in Toman (not Rial).
price_minNoPrice in Toman (not Rial).
brand_modelNoExact brand/model string, e.g. "samsung galaxy s21 5g" (from divar_get_post).
district_idsNoDivar numeric district ids (e.g. ["208"]). Get them from divar_get_post district_id.
max_age_hoursNoDrop posts older than this (Divar's own recency filter is unreliable; this is client-side).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation is read-only and requires no account, and it reveals cursor pagination and the exact normalized return fields, all beyond what the schema alone provides.

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 roughly 80 words, front-loaded with the main purpose and followed by compact feature and return-value statements. Every sentence carries useful information, though the enumeration of parameters partially duplicates schema content.

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?

Given 13 parameters and no output schema, this description covers key contextual aspects: read-only access, no account requirement, live listings, cursor pagination, and exact normalized row fields. It does not describe error behavior or page/limit interaction, but these are minor given the thorough schema.

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%, so the baseline is 3. The description restates the parameter categories (query, city, category, Toman price range, photo-only, district ids, brand/model) but adds no new semantic meaning beyond the schema's own parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific action, 'Search live divar.ir listings', naming the resource and context. It clearly states what the tool does, though it does not explicitly differentiate it from sibling tools like divar_get_post or divar_price_analysis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives such as divar_get_post or divar_similar_posts. It mentions read-only/no account, which implies safe general searching, but it does not tell the agent when to prefer this over sibling tools.

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

Deploy Server

Other Tools