Product Data Tools MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_TOKEN | No | API token for Bright Data | |
| APIFY_TOKEN | No | API token for Apify Actors | |
| BROWSER_ZONE | No | Browser zone for Bright Data | |
| WEB_UNLOCKER_ZONE | No | Web unlocker zone for Bright Data |
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 |
|---|---|
| query_store_productsA | Retrieves product data from a specific store based on filtering and sorting criteria. Uses a separate Product Data Server to fetch information. Args: store_name: The name of the store to search within (e.g., 'aeropress_product_cleaned'). This is required. filter_criteria: Optional. A dictionary specifying filter criteria. Keys are field names (e.g., 'price', 'rating'). Values are either exact match values (e.g., {'rating': 4.5}) or dictionaries for operators (e.g., {'price': {'operator': '<', 'value': 50.0}}). Supported operators by the data server include '==', '!=', '<', '>', '<=', '>='. Consult data server documentation (or the available_fields tool) for available fields and operators. sort_by: Optional. The field name to sort the results by (e.g., 'price', 'rating', 'score'). If not specified, the data server might default to 'score' or its own internal default. sort_order: Optional. The order of sorting ('asc' for ascending, 'desc' for descending). Defaults to 'desc'. limit: Optional. The maximum number of products to return. Defaults to 10. fields: Optional. A list of specific fields to include in the results (e.g., ['product_name', 'price', 'product_url']). If not specified, the data server returns all available fields for the matching products. Returns: A list of product dictionaries matching the criteria on success. Returns a string error message if the data server cannot be reached, the store is not found, or if there's an error during the query. |
| get_overall_top_productsA | Retrieves the top K products across all stores. Args: k: The number of top products to return. Defaults to 10. Must be a positive integer. sort_by: Optional. The field to sort by (e.g., 'score', 'price'). Defaults to 'score' on the data server. sort_order: Optional. The order of sorting ('asc' or 'desc'). Defaults to 'desc'. fields: Optional. A list of specific fields to include. Defaults to all available fields. Returns: A list of product dictionaries for the top products, or a string error message. |
| get_product_details_by_urlA | Retrieves detailed information for specific products using their URLs. Queries the separate Product Data Server. Note: The data server expects product_ids, but the client library method takes product_urls. Ensure the data server can correctly map these URLs to its internal product_ids if necessary. Args: product_urls: A list of product URLs for which to retrieve details. Required. fields: Optional. A list of specific fields to include. Defaults to all available fields. Returns: A list of product dictionaries for the found products, or a string error message. |
| get_available_fieldsA | Retrieves the list of available data fields (columns) for filtering and sorting. Queries the separate Product Data Server. Args: store_name: Optional. The name of the store to check fields for. If omitted, returns fields available across all stores. Returns: A dictionary containing a list of available fields (e.g., {'available_fields': [...]}), or a string error message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ABAKHAR721/data_mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server