Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Search products

dk_search
Read-onlyIdempotent

Search Digikala products by Persian or English name and refine results by price, brand, color, seller, availability, and attributes, with sorting and pagination.

Instructions

Search products by name: price (Toman), discount, seller, rating, 20 per page.

Each product has match ('all', 'some' + missing_words, 'none'); prefer 'all'. Filter ids: dk_filters(query=...).

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": {
      "query": "<query>"
    },
    "name": "dk_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNorelevance
queryYesPersian or English words, e.g. 'گوشی سامسونگ'.
colorsNoColor ids from dk_filters.
brand_idsNoBrand ids (dk_product brand_id), e.g. [18] Samsung.
max_priceNo
min_priceNo
attributesNo{attribute id: [value ids]} from dk_filters, e.g. {2226: [19239]}. Values OR, attributes AND.
seller_typeNo
fast_deliveryNoJet delivery only.
in_stock_onlyNo
ready_to_shipNoIn Digikala's warehouse only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed33 schema fields changedv0.6.0
    • addedInput schema / properties / attributes / additionalProperties
      Added value: +{
      +  "items": {
      +    "type": "integer"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • removedInput schema / properties / attributes / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": {
      -      "items": {
      -        "type": "integer"
      -      },
      -      "maxItems": 20,
      -      "type": "array"
      -    },
      -    "maxProperties": 10,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / attributes / description
      Previous value: -"Feature filters from dk_filters: {attribute id: [value ids]}, e.g. {2226: [19239]}. Values OR, attributes AND."New value: +"{attribute id: [value ids]} from dk_filters, e.g. {2226: [19239]}. Values OR, attributes AND."
    • addedInput schema / properties / attributes / maxProperties
      Added value: +10
    • addedInput schema / properties / attributes / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • removedInput schema / properties / brand_ids / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "integer"
      -    },
      -    "maxItems": 5,
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / brand_ids / description
      Previous value: -"Brand ids from dk_product's brand_id or dk_brand_products' brand.id, e.g. [18] Samsung, [1662] Xiaomi."New value: +"Brand ids (dk_product brand_id), e.g. [18] Samsung."
    • addedInput schema / properties / brand_ids / items
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / brand_ids / maxItems
      Added value: +5
    • addedInput schema / properties / brand_ids / type
      Added value: +[
      +  "array",
      +  "null"
      +]
    • removedInput schema / properties / colors / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "integer"
      -    },
      -    "maxItems": 10,
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / colors / description
      Previous value: -"Color ids from dk_filters, e.g. [1]."New value: +"Color ids from dk_filters."
    • addedInput schema / properties / colors / items
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / colors / maxItems
      Added value: +10
    • addedInput schema / properties / colors / type
      Added value: +[
      +  "array",
      +  "null"
      +]
    • changedInput schema / properties / fast_delivery / description
      Previous value: -"Only items with fast (Jet) delivery."New value: +"Jet delivery only."
    • removedInput schema / properties / in_stock_only / description
      Removed value: -"Only products that can be bought now."
    • removedInput schema / properties / max_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / max_price / description
      Removed value: -"Highest price in Toman, e.g. 50000000."
    • addedInput schema / properties / max_price / minimum
      Added value: +0
    • addedInput schema / properties / max_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / min_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / min_price / description
      Removed value: -"Lowest price in Toman, e.g. 10000000 for 10 million Toman."
    • addedInput schema / properties / min_price / minimum
      Added value: +0
    • addedInput schema / properties / min_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / page / description
      Removed value: -"Page number, from 1 (20 products per page)."
    • changedInput schema / properties / query / description
      Previous value: -"Product name or words, Persian or English, e.g. 'گوشی سامسونگ' or 'airpods pro'."New value: +"Persian or English words, e.g. 'گوشی سامسونگ'."
    • changedInput schema / properties / ready_to_ship / description
      Previous value: -"Only items already in Digikala's warehouse (ship sooner)."New value: +"In Digikala's warehouse only."
    • removedInput schema / properties / seller_type / anyOf
      Removed value: -[
      -  {
      -    "enum": [
      -      "digikala",
      -      "official",
      -      "trusted",
      -      "roosta"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / seller_type / description
      Removed value: -"Only offers from Digikala itself, official brand sellers, trusted sellers or rural (roosta) sellers."
    • addedInput schema / properties / seller_type / enum
      Added value: +[
      +  "digikala",
      +  "official",
      +  "trusted",
      +  "roosta",
      +  null
      +]
    • addedInput schema / properties / seller_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / sort / description
      Removed value: -"Order of the results."
  2. Changed16 schema fields changedv0.4.0
    • changedInput schema / properties / attributes / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {
      -      "items": {
      -        "type": "integer"
      -      },
      -      "type": "array"
      -    },
      -    "maxProperties": 10,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {
      +      "items": {
      +        "type": "integer"
      +      },
      +      "maxItems": 20,
      +      "type": "array"
      +    },
      +    "maxProperties": 10,
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / attributes / description
      Previous value: -"Feature filters from dk_filters: {attribute id: [value ids]}, e.g. {2226: [19239]} for Android phones. Values of one attribute are OR'ed, attributes are AND'ed."New value: +"Feature filters from dk_filters: {attribute id: [value ids]}, e.g. {2226: [19239]}. Values OR, attributes AND."
    • removedInput schema / properties / attributes / title
      Removed value: -"Attributes"
    • removedInput schema / properties / brand_ids / title
      Removed value: -"Brand Ids"
    • removedInput schema / properties / colors / title
      Removed value: -"Colors"
    • removedInput schema / properties / fast_delivery / title
      Removed value: -"Fast Delivery"
    • removedInput schema / properties / in_stock_only / title
      Removed value: -"In Stock Only"
    • removedInput schema / properties / max_price / title
      Removed value: -"Max Price"
    • removedInput schema / properties / min_price / title
      Removed value: -"Min Price"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / ready_to_ship / title
      Removed value: -"Ready To Ship"
    • removedInput schema / properties / seller_type / title
      Removed value: -"Seller Type"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"dk_searchArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_searchDictOutput",
      -  "type": "object"
      -}New value: +null
  3. Changed5 schema fields changedv0.2.1
    • addedInput schema / properties / attributes
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "items": {
      +          "type": "integer"
      +        },
      +        "type": "array"
      +      },
      +      "maxProperties": 10,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Feature filters from dk_filters: {attribute id: [value ids]}, e.g. {2226: [19239]} for Android phones. Values of one attribute are OR'ed, attributes are AND'ed.",
      +  "title": "Attributes"
      +}
    • addedInput schema / properties / colors
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "integer"
      +      },
      +      "maxItems": 10,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Color ids from dk_filters, e.g. [1].",
      +  "title": "Colors"
      +}
    • addedInput schema / properties / fast_delivery
      Added value: +{
      +  "default": false,
      +  "description": "Only items with fast (Jet) delivery.",
      +  "title": "Fast Delivery",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / ready_to_ship
      Added value: +{
      +  "default": false,
      +  "description": "Only items already in Digikala's warehouse (ship sooner).",
      +  "title": "Ready To Ship",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / seller_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "digikala",
      +        "official",
      +        "trusted",
      +        "roosta"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only offers from Digikala itself, official brand sellers, trusted sellers or rural (roosta) sellers.",
      +  "title": "Seller Type"
      +}
  4. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavioral context: a fixed page size of 20, price denominated in Toman, and the three-state match contract ('all', 'some' + missing_words, 'none') with a recommendation. It omits whether results are cached or how many pages exist, which keeps it from a 5.

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?

Two short blocks, front-loaded with the capability and followed by the matching/filter guidance; nothing is redundant with the title. The telegraphic style ('price (Toman), discount, seller, rating') is compact but slightly ambiguous as to whether those are inputs or outputs.

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?

With 12 parameters, no output schema, and 50% schema description coverage, the description carries a fair burden. It covers the result shape partially (match states, page size) and the filter-id workflow, but leaves the sort options, stock/shipping flags, and how attributes combine only half-explained. Adequate to call correctly for simple queries, incomplete for a fully specified filtered search.

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 50%, so the description must compensate for roughly half the 12 parameters. It clarifies price units, the discount/seller/rating filters, pagination size, and the match semantics that the schema does not define. It leaves sort, colors, attributes combination logic, in_stock_only, and ready_to_ship unexplained in prose, so coverage of the low-documented parameters is only partial.

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 gives a specific verb and resource ('Search products') and enumerates the axis it searches over: name, price in Toman, discount, seller, rating, with 20 results per page. An agent knows exactly what this tool returns. It stops short of distinguishing itself from close siblings like dk_brand_products or dk_category_products, so it is clear but not sibling-differentiating.

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

Usage Guidelines3/5

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

It gives one concrete routing hint – fetch filter ids via dk_filters(query=...) – and advises preferring match='all'. That is real guidance for a specific sub-case. It does not say when to pick this over dk_suggest, dk_fresh_search, dk_find_cheapest, or dk_similar, so alternatives remain implied rather than stated.

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