Skip to main content
Glama

update-collection

Modify Shopify collection details including title, description, and SEO metadata to keep store content current and optimized for search engines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionIdYesThe GID of the collection to update (e.g., "gid://shopify/Collection/1234567890")
titleNo
descriptionNo
descriptionHtmlNo
seoNo

Implementation Reference

  • The main handler function 'execute' that performs the GraphQL mutation to update the Shopify collection using the provided input data, handles errors, and returns the updated collection information.
    execute: async (input: UpdateCollectionInput) => {
      try {
        const { collectionId, ...updateData } = input;
    
        const mutation = gql`
          mutation collectionUpdate($input: CollectionInput!) {
            collectionUpdate(input: $input) {
              collection {
                id
                title
                handle
                description
                descriptionHtml
                updatedAt
                seo {
                  title
                  description
                }
              }
              userErrors {
                field
                message
              }
            }
          }
        `;
    
        const variables = {
          input: {
            id: collectionId,
            ...updateData
          }
        };
    
        const data = await shopifyClient.request(mutation, variables) as {
          collectionUpdate: {
            collection: {
              id: string;
              title: string;
              handle: string;
              description: string;
              descriptionHtml: string;
              updatedAt: string;
              seo: {
                title: string;
                description: string;
              };
            };
            userErrors: Array<{
              field: string;
              message: string;
            }>;
          };
        };
    
        if (data.collectionUpdate.userErrors.length > 0) {
          throw new Error(
            `Failed to update collection: ${data.collectionUpdate.userErrors
              .map((error) => error.message)
              .join(", ")}`
          );
        }
    
        return {
          collection: data.collectionUpdate.collection
        };
      } catch (error) {
        console.error("Error updating collection:", error);
        throw new Error(
          `Failed to update collection: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
      }
    }
  • Zod schema defining the input parameters for the update-collection tool, including collectionId (required) and optional fields like title, description, seo.
    const UpdateCollectionInputSchema = z.object({
      collectionId: z.string().min(1).describe("The GID of the collection to update (e.g., \"gid://shopify/Collection/1234567890\")"),
      title: z.string().optional().describe("The new title for the collection"),
      description: z.string().optional().describe("The new description for the collection"),
      descriptionHtml: z.string().optional().describe("The new HTML description for the collection"),
      seo: z.object({
        title: z.string().optional(),
        description: z.string().optional()
      }).optional().describe("SEO information for the collection")
    });
  • src/index.ts:136-154 (registration)
    Registration of the 'update-collection' tool in the MCP server, using an inline Zod schema and delegating execution to the imported updateCollection.execute function.
    server.tool(
      "update-collection",
      {
        collectionId: z.string().min(1).describe("The GID of the collection to update (e.g., \"gid://shopify/Collection/1234567890\")"),
        title: z.string().optional(),
        description: z.string().optional(),
        descriptionHtml: z.string().optional(),
        seo: z.object({
          title: z.string().optional(),
          description: z.string().optional()
        }).optional()
      },
      async (args) => {
        const result = await updateCollection.execute(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result) }]
        };
      }
    );
  • src/index.ts:15-15 (registration)
    Import statement for the updateCollection tool module.
    import { updateCollection } from "./tools/updateCollection.js";
  • src/index.ts:73-73 (registration)
    Initialization of the updateCollection tool with the Shopify GraphQL client.
    updateCollection.initialize(shopifyClient);
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/luckyfarnon/Shopify-MCP'

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