Skip to main content
Glama

get_collection

Retrieve a Shopify collection by its global ID, including title, handle, sort order, description, and optional product list. Set productsFirst to 0 for metadata only.

Instructions

Fetch a single collection by GID with full details — title, handle, sort order, description, and the first N products inside it. Pass productsFirst=0 for metadata-only when you don't need the products array. Returns a friendly text view; pageInfo flags when more products exist beyond the requested page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCollection GID, e.g. 'gid://shopify/Collection/123456'. Get one from list_collections.
productsFirstNoHow many products to include alongside the collection. Pass 0 to skip products entirely (faster for collection-only metadata).

Implementation Reference

  • The main handler function for the 'get_collection' tool. It calls the GraphQL query, checks if the collection was found, formats the response with collection metadata and its products, and returns a text-based result.
    server.tool(
      "get_collection",
      "Fetch a single collection by GID with full details — title, handle, sort order, description, and the first N products inside it. Pass productsFirst=0 for metadata-only when you don't need the products array. Returns a friendly text view; pageInfo flags when more products exist beyond the requested page.",
      getCollectionSchema,
      async (args) => {
        const data = await client.graphql<{
          collection:
            | (Collection & {
                products: {
                  edges: Array<{
                    node: {
                      id: string;
                      title: string;
                      handle: string;
                      status: string;
                      featuredImage?: { url: string } | null;
                    };
                  }>;
                  pageInfo: { hasNextPage: boolean };
                };
              })
            | null;
        }>(GET_COLLECTION_QUERY, {
          id: args.id,
          productsFirst: args.productsFirst,
        });
        if (!data.collection) {
          return {
            content: [
              { type: "text" as const, text: `Collection not found: ${args.id}` },
            ],
          };
        }
        const c = data.collection;
        const productLines = c.products.edges.map(
          ({ node }) => `    - ${node.title} [${node.status}] (${node.handle}) — ${node.id}`,
        );
        return {
          content: [
            {
              type: "text" as const,
              text: [
                `${c.title}`,
                `  ID: ${c.id}`,
                `  Handle: ${c.handle}`,
                `  Sort order: ${c.sortOrder ?? "(default)"}`,
                c.description ? `  Description: ${c.description}` : "",
                `  Products (${c.productsCount?.count ?? "?"}):`,
                ...productLines,
                c.products.pageInfo.hasNextPage
                  ? "  (more products available; raise productsFirst to page further)"
                  : "",
              ]
                .filter(Boolean)
                .join("\n"),
            },
          ],
        };
      },
    );
  • The Zod schema for the 'get_collection' tool, defining required 'id' (collection GID) and optional 'productsFirst' (number of products to include) parameters.
    const getCollectionSchema = {
      id: z
        .string()
        .describe(
          "Collection GID, e.g. 'gid://shopify/Collection/123456'. Get one from list_collections.",
        ),
      productsFirst: z
        .number()
        .int()
        .min(0)
        .max(100)
        .default(20)
        .describe(
          "How many products to include alongside the collection. Pass 0 to skip products entirely (faster for collection-only metadata).",
        ),
    };
  • The GET_COLLECTION_QUERY GraphQL query used by the handler to fetch collection details including products.
    const GET_COLLECTION_QUERY = /* GraphQL */ `
      query GetCollection($id: ID!, $productsFirst: Int!) {
        collection(id: $id) {
          id
          handle
          title
          description
          sortOrder
          updatedAt
          image { url altText }
          productsCount { count }
          products(first: $productsFirst) {
            edges {
              node {
                id
                title
                handle
                status
                featuredImage { url }
              }
            }
            pageInfo { hasNextPage endCursor }
          }
        }
      }
    `;
  • The registration of 'get_collection' with the MCP server via server.tool(), with its name, description, schema reference, and handler.
    server.tool(
      "get_collection",
      "Fetch a single collection by GID with full details — title, handle, sort order, description, and the first N products inside it. Pass productsFirst=0 for metadata-only when you don't need the products array. Returns a friendly text view; pageInfo flags when more products exist beyond the requested page.",
      getCollectionSchema,
Behavior3/5

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

No annotations provided, so description carries full burden. States return is a 'friendly text view' and that pageInfo flags product existence. Lacks details on idempotency, authorization needs, or whether it's a pure read operation.

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?

Two clear, well-structured sentences. Front-loads purpose, no fluff. Every sentence provides actionable information.

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

Completeness4/5

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

Given no output schema, description adequately covers return fields (title, handle, etc.) and pagination info. Could mention error cases or format details for a higher score.

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?

Both parameters documented in schema (100% coverage). Description adds value by explaining practical use of productsFirst=0 and pageInfo behavior, going beyond schema definitions.

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 uses specific verb 'Fetch' and specifies resource 'single collection by GID' with detailed fields (title, handle, etc.). Clearly distinguishes from sibling tools like list_collections or create_collection.

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

Usage Guidelines4/5

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

Provides explicit guidance for using productsFirst=0 for metadata-only. Mentions pageInfo for pagination, but could be more explicit about when to prefer this over list_collections or other collection tools.

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/miller-joe/shopify-mcp'

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