Skip to main content
Glama
smithery-ai

Shopify Update MCP Server

by smithery-ai

get-shop-details

Retrieve comprehensive Shopify store information including shipping countries and operational details for integration and analysis purposes.

Instructions

Get extended shop details including shipping countries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:553-571 (registration)
    Registration of the 'get-shop-details' MCP tool, including empty input schema and inline handler function that instantiates ShopifyClient and delegates to loadShopDetail method.
    server.tool(
      "get-shop-details",
      "Get extended shop details including shipping countries",
      {},
      async () => {
        const client = new ShopifyClient();
        try {
          const shopDetails = await client.loadShopDetail(
            SHOPIFY_ACCESS_TOKEN,
            MYSHOPIFY_DOMAIN
          );
          return {
            content: [{ type: "text", text: JSON.stringify(shopDetails, null, 2) }],
          };
        } catch (error) {
          return handleError("Failed to retrieve extended shop details", error);
        }
      }
    );
  • Core handler logic in ShopifyClient.loadShopDetail: performs GraphQL query to fetch extended shop details (shipsToCountries). Called by the tool handler.
    async loadShopDetail(
      accessToken: string,
      shop: string
    ): Promise<ShopResponse> {
      const myshopifyDomain = await this.getMyShopifyDomain(accessToken, shop);
    
      const graphqlQuery = gql`
        {
          shop {
            shipsToCountries
          }
        }
      `;
    
      const res = await this.shopifyGraphqlRequest<ShopResponse>({
        url: `https://${myshopifyDomain}/admin/api/${this.SHOPIFY_API_VERSION}/graphql.json`,
        accessToken,
        query: graphqlQuery,
      });
    
      return res.data;
    }
  • Helper method getMyShopifyDomain used by loadShopDetail to resolve the myshopify domain from shop details.
    private async getMyShopifyDomain(
      accessToken: string,
      shop: string
    ): Promise<string> {
      // POST requests are getting converted into GET on custom domain, so we need to retrieve the myshopify domain from the shop object
      const loadedShop = await this.loadShop(accessToken, shop);
      return loadedShop.shop.myshopify_domain;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying it's read-only and non-destructive, but doesn't confirm this explicitly or add other behavioral traits like rate limits, authentication needs, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Get extended shop details') and adds a specific detail ('including shipping countries'). There's no wasted verbiage, repetition, or unnecessary elaboration, making it highly concise and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what data is retrieved but lacks context about the return format, error conditions, or how it differs from similar tools. For a read-only data fetch, this is passable but leaves clear gaps in completeness.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100% (though trivial with no properties). The description adds no parameter information, which is appropriate here. Baseline for 0 parameters is 4, as there's nothing to document beyond the schema, and the description doesn't need to compensate for any gaps.

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

Purpose4/5

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

The description clearly states the action ('Get') and resource ('extended shop details'), specifying the inclusion of 'shipping countries' as a key data point. It distinguishes this tool from 'get-shop' (presumably a basic version) by emphasizing 'extended' details. However, it doesn't explicitly differentiate from all siblings like 'get-collections' or 'get-products', keeping it at 4 rather than 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'get-shop-details' over 'get-shop' (a likely sibling for basic info) or other data-fetching tools like 'get-products'. There's no context about prerequisites, timing, or exclusions, leaving usage entirely implicit.

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/smithery-ai/shopify-mcp-server-main-1'

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