Digikala MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_optimized_keywords_and_categoriesA | Get optimized search keywords and relevant categories. IMPORTANT: Always call this with BOTH Persian (Farsi) and English queries separately, as the API responds differently to each language and Farsi typically yields better, more comprehensive results. |
| search_productsA | Search for products within a specific category with filtering and sorting. Returns 20 products per page. CRITICAL WORKFLOW: ALWAYS call get_optimized_keywords_and_categories FIRST to get the category_id for your search - this API requires it. Use the keyword-category pairs from that response. Search with BOTH Persian (Farsi) and English keywords separately - they produce different results, with Farsi often being more comprehensive. All prices in TOOMAN (1 Tooman = 10 Rials). |
| get_product_detailsA | Get comprehensive product information including specifications, expert reviews, customer feedback, and buy suggestions. Use this when you need detailed information about a specific product. |
| get_product_recommendationsA | Get similar products and related category recommendations. Use this when a product is close but not exactly what you need, to explore similar alternatives. |
| search_text_lenzA | AI-powered semantic search using Text-Lenz. Exceptional for clothing, accessories, wearables, and shoes. Use 2-3 word visual descriptions (e.g., 'red summer dress', 'black running shoes'). Understands natural language and context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools have mostly distinct purposes, with clear boundaries: get_optimized_keywords_and_categories for keyword/category optimization, get_product_details for detailed product info, get_product_recommendations for similar products, search_products for category-based searches, and search_text_lenz for semantic visual searches. However, search_products and search_text_lenz both involve searching, which could cause minor confusion, though their descriptions clarify different use cases (category-based vs. semantic/visual).
Tool names follow a consistent verb_noun pattern with underscores (e.g., get_optimized_keywords_and_categories, search_products), making them predictable and readable. There is a minor deviation with search_text_lenz, which includes a brand name 'Text-Lenz' in the noun part, but it still fits the overall naming convention without mixing styles like camelCase.
With 5 tools, this server is well-scoped for an e-commerce product search and information domain. Each tool serves a specific function (e.g., optimization, details, recommendations, searches), and none feel redundant or unnecessary, providing a balanced set for typical agent workflows in this context.
The tool set covers key operations like searching, getting details, and recommendations, but there are notable gaps. For example, there are no tools for user account management (e.g., login, cart operations), purchase-related actions (e.g., add to cart, checkout), or content management (e.g., reviews, ratings). While the domain appears focused on product discovery and information, these omissions could limit agent functionality in full e-commerce scenarios.