Ask questions across Shopify, Klaviyo, GA4 and 20+ e-commerce sources in plain English.
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.
Average 4.5/5 across 75 of 75 tools scored. Lowest: 3.8/5.
Many tools have overlapping purposes (multiple daily revenue series, multiple CVR sources, product/inventory velocity variants), so an agent must read descriptions carefully to pick correctly. However, the extensive disambiguation notes and clear usage guidance reduce ambiguity, making it more navigable than the raw count suggests.
The dominant patterns are get_* for reads and save_*/update_*/set_* for writes, but there are notable inconsistencies: query_orders vs get_orders, record_metric_snapshot vs save_*, set_intervention vs save_*, and the outlier ask_moby. The mix is readable but not fully predictable.
75 tools is far beyond the reasonable threshold for an agent to manage effectively, even for a comprehensive Shopify data connector. The scale explicitly marks 50+ as an extreme mismatch, and this server far exceeds that.
The tool set covers nearly every facet of e-commerce analytics and internal operational tracking: orders, customers, products, inventory, marketing, SEO, reviews, support, plus insights, interventions, focus plans, targets, and wakeups. No significant gaps or dead ends are apparent for the stated purpose.
get_subscription_statusAInspectThe Ask AI trial or subscription for this account has ended, so the data tools are paused. Call this to get the account status and the reactivation link to share with the user. Connected data sources and history are preserved and reactivate instantly on subscribing.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that data sources and history are preserved and reactivate instantly, implying a non-destructive read operation. This adds useful behavioral context beyond the bare function.
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?
Three concise sentences: the trigger condition, what to do, and reassurance about data preservation. Every sentence contributes necessary context, with no redundancy or filler.
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?
The description covers the reason for the call, the expected output (status and reactivation link), and the post-subscription behavior. Given the tool's simplicity with no parameters and no output schema, this is fully complete.
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?
There are zero parameters and 100% schema coverage is trivially present. The description adds no parameter-specific details because none are needed, which matches the baseline for no-parameter tools.
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?
The description explicitly states the tool retrieves the account status and the reactivation link, with specific context that the trial or subscription has ended. This is a clear verb+resource combination that fully clarifies the tool's function.
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?
The description gives a clear trigger scenario: when the trial/subscription has ended and data tools are paused. It also instructs to share the link with the user. While no alternatives are listed, no siblings exist, and the 'when' guidance is concrete.
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.
No comments yet. Be the first to start the discussion!
