Product Info Extractor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host address to bind to | 0.0.0.0 |
| PORT | No | Port to run the server on | 3000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_product_infoA | Extract comprehensive product information from e-commerce URLs including images, stock availability, product variants (color-by-size inventory), price, dimensions, and specifications |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap. The tool's purpose is clearly defined and distinct.
The single tool name 'extract_product_info' follows a clear verb_noun convention. Though there is only one tool, the naming is consistent with standard practices.
The server has only one tool, which falls into the borderline range. While the tool is broad and covers the stated purpose well, the count feels thin for a typical MCP server.
The tool description covers all major aspects of product information extraction: images, stock, variants, price, dimensions, and specifications. No obvious gaps exist for the stated domain.