Skip to main content
Glama

list_ecommerce_stores

Retrieve connected e-commerce stores (Shopify, WooCommerce) along with their revenue statistics to monitor performance.

Instructions

List connected e-commerce stores (Shopify, WooCommerce, etc.) with revenue stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'list_ecommerce_stores' tool. It calls the Mailchimp API GET /ecommerce/stores and formats the response with store details (id, name, platform, domain, list_id, currency_code, money_format, is_syncing, created_at).
    @mcp.tool()
    async def list_ecommerce_stores(count: int = 20) -> str:
        """List connected e-commerce stores (Shopify, WooCommerce, etc.) with revenue stats."""
        mc = get_client()
        data = await mc.get("/ecommerce/stores", params={"count": min(count, 100)})
        stores = []
        for s in data.get("stores", []):
            stores.append({
                "id": s.get("id", ""),
                "name": s.get("name", ""),
                "platform": s.get("platform", ""),
                "domain": s.get("domain", ""),
                "list_id": s.get("list_id", ""),
                "currency_code": s.get("currency_code", ""),
                "money_format": s.get("money_format", ""),
                "is_syncing": s.get("is_syncing", False),
                "created_at": s.get("created_at", ""),
            })
        return _fmt({"total_items": data.get("total_items", 0), "stores": stores})
  • The tool is registered via the @mcp.tool() decorator on line 1322, making it available as an MCP tool named 'list_ecommerce_stores'.
    @mcp.tool()
    async def list_ecommerce_stores(count: int = 20) -> str:
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It implies a read-only operation but does not explicitly state that or disclose any behavioral traits (e.g., rate limits, prerequisites). Adequate for a simple listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, front-loaded sentence with no extraneous words. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Has an output schema, so return values need not be explained. However, missing parameter explanation and lack of context about filtering or pagination make it minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fails to explain the 'count' parameter. It provides no additional meaning beyond the schema's type and default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists e-commerce stores with examples (Shopify, WooCommerce) and includes revenue stats, distinguishing it from sibling tools like list_store_orders or list_store_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like list_store_carts or list_store_orders. The description only states what it does, not when it's appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/AlexlaGuardia/mcp-mailchimp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server