Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Product reviews

dk_reviews
Read-onlyIdempotent

Read a Digikala product’s customer reviews with star ratings, pros and cons, verified-buyer flags, sorting, and optional full text to assess buyer feedback.

Instructions

Read customer reviews: stars 1-5 (null = none), text, pros/cons, verified buyer flag.

Texts are cut to 300 characters, pros/cons to 5 of 80 (full_text=true: whole).

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": {
      "product_id": "<product_id>"
    },
    "name": "dk_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNomost_helpful
limitNoOf the page's 20.
full_textNoNo text cuts.
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / full_text / description
      Previous value: -"Skip text cuts and pros/cons caps; return everything whole."New value: +"No text cuts."
    • changedInput schema / properties / limit / description
      Previous value: -"Max reviews from the page (20 per page)."New value: +"Of the page's 20."
    • removedInput schema / properties / page / description
      Removed value: -"Page number, from 1 (20 products per page)."
    • removedInput schema / properties / product_id / description
      Removed value: -"Digikala product id, the number in 'dkp-<id>' (from dk_search etc.), e.g. 20109389."
    • removedInput schema / properties / sort / description
      Removed value: -"Order of the reviews."
  2. Changed7 schema fields changedv0.4.0
    • addedInput schema / properties / full_text
      Added value: +{
      +  "default": false,
      +  "description": "Skip text cuts and pros/cons caps; return everything whole.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 10,
      +  "description": "Max reviews from the page (20 per page).",
      +  "maximum": 20,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"dk_reviewsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_reviewsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, open-world read, so the burden is lowered. The description adds non-obvious behavior the annotations and schema do not: exact truncation limits (300 chars, 5 pros/cons at 80 chars) and how to lift them. It lacks mention of pagination limits or total counts, keeping it below 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 compact sentences, front-loaded with the return shape and then the truncation caveat. The telegraphic style ('5 of 80', 'whole') is dense but slightly ambiguous, which costs a point.

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?

With no output schema and 40% schema coverage, the description usefully documents what comes back and how it is truncated. The main remaining gap is that sort options and page/limit interplay are left entirely to the 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 coverage is 40%, so the description must compensate. It explains full_text well (default cut to 300 chars, pros/cons to 5 of 80), but says nothing about page, sort (most_helpful/newest/buyers_first), or the meaning of limit beyond the schema's 'Of the page's 20'. The stars 'null = none' note is a useful clarification of returned data rather than of a parameter.

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 verb and resource ('Read customer reviews') and enumerates the returned fields (stars, text, pros/cons, verified buyer flag), which distinguishes it from dk_questions (Q&A) and dk_product (product data). It does not explicitly name a sibling alternative, so it stops short of a 5.

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?

There is no statement of when to call this tool versus alternatives, nor any prerequisite (e.g. needing a product_id from dk_search/dk_product). The only conditional mentioned, full_text=true, is parameter guidance rather than usage guidance.

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