E-Commerce Intelligence MCP Server
Server Details
MCP server for e-commerce intelligence including product data, pricing analytics, Amazon listings, and market trends for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3/5 across 2 of 2 tools scored.
The tools have clearly distinct purposes: one analyzes store metadata (tech stack, theme, traffic) while the other retrieves product catalog data. No functional overlap exists between analyzing store infrastructure and listing products.
Both tools use snake_case with verb_noun structure (analyze_shopify_store, get_store_products). Minor inconsistency in domain specificity—one includes 'shopify' while the other uses generic 'store'—but patterns are predictable and readable.
Two tools is borderline thin for an 'E-Commerce Intelligence' server. While sufficient for basic store inspection, the scope suggests need for competitor comparison, price tracking, or trend analysis tools that are absent.
Significant gaps exist for e-commerce intelligence workflows. Missing comparison capabilities, historical price tracking, review analysis, sales estimation beyond traffic, or competitor benchmarking. Agents will hit dead ends when asked for competitive intelligence or market analysis.
Available Tools
2 toolsanalyze_shopify_storeBRead-onlyInspect
Analyze a Shopify e-commerce store to extract technology stack, theme, installed apps, estimated traffic, and store performance metrics. Returns theme name, app list, tech integrations, traffic estimate, conversion data, and competitive insights. Use for competitive intelligence, market research, or e-commerce benchmarking.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Shopify store URL (e.g. 'https://www.example-store.myshopify.com' or 'example-store.com') |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations or output schema, the description discloses what data is returned (tech stack, etc.), but omits side effects or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise single sentence with purpose front-loaded, though brevity sacrifices necessary parameter details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a single-parameter tool; compensates for missing output schema by listing return values, but lacks parameter guidance.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% coverage and description fails to compensate—the 'url' parameter receives no explanation of format (domain vs full URL).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specifically lists outputs (tech stack, theme, apps, traffic) distinguishing it from sibling 'get_store_products' which likely retrieves product data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus the sibling tool or other alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_store_productsBRead-onlyInspect
Extract all products from a Shopify store including titles, descriptions, images, pricing, variants, and inventory status. Returns product catalog with URLs for each item. Use for competitor product research, price monitoring, or market basket analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Shopify store URL to scrape products from (e.g. 'store-name.myshopify.com') | |
| max_results | No | Maximum products to retrieve (default 50, higher values for full catalog export) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses what data fields are returned (prices, titles, images) but omits other behavioral details like pagination behavior, rate limits, or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise single sentence that is front-loaded with the action, though brevity limits completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple tool but lacks important context such as pagination details (relevant given max_results parameter) and authentication requirements.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Fails to compensate for 0% schema description coverage; does not clarify what the 'url' should contain (store homepage vs API endpoint) or explain 'max_results' behavior.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool retrieves product listings from Shopify stores and specifies returned data fields, implicitly distinguishing it from the sibling 'analyze' tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no explicit guidance on when to use this tool versus alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!