Skip to main content
Glama

update-page

Modify Shopify store pages by updating titles, content, SEO metadata, and publication status using the page's unique identifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYesThe GID of the page to update (e.g., "gid://shopify/Page/1234567890")
titleNo
bodyNo
bodyHtmlNo
seoNo
publishedNo

Implementation Reference

  • The execute function of the updatePage tool that sends a GraphQL mutation to Shopify to update the specified page with the provided input data, handles errors, and returns the updated page information.
    execute: async (input: UpdatePageInput) => {
      try {
        const { pageId, ...updateData } = input;
    
        const mutation = gql`
          mutation pageUpdate($input: PageInput!) {
            pageUpdate(input: $input) {
              page {
                id
                title
                handle
                bodySummary
                body
                bodyHtml
                updatedAt
                publishedAt
                seo {
                  title
                  description
                }
              }
              userErrors {
                field
                message
              }
            }
          }
        `;
    
        const variables = {
          input: {
            id: pageId,
            ...updateData
          }
        };
    
        const data = await shopifyClient.request(mutation, variables) as {
          pageUpdate: {
            page: {
              id: string;
              title: string;
              handle: string;
              bodySummary: string;
              body: string;
              bodyHtml: string;
              updatedAt: string;
              publishedAt: string;
              seo: {
                title: string;
                description: string;
              };
            };
            userErrors: Array<{
              field: string;
              message: string;
            }>;
          };
        };
    
        if (data.pageUpdate.userErrors.length > 0) {
          throw new Error(
            `Failed to update page: ${data.pageUpdate.userErrors
              .map((error) => error.message)
              .join(", ")}`
          );
        }
    
        return {
          page: data.pageUpdate.page
        };
      } catch (error) {
        console.error("Error updating page:", error);
        throw new Error(
          `Failed to update page: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
      }
    }
  • Zod input schema defining the parameters for updating a page, including pageId, title, body, bodyHtml, seo, and published status.
    const UpdatePageInputSchema = z.object({
      pageId: z.string().min(1).describe("The GID of the page to update (e.g., \"gid://shopify/Page/1234567890\")"),
      title: z.string().optional().describe("The new title for the page"),
      body: z.string().optional().describe("The new body content for the page"),
      bodyHtml: z.string().optional().describe("The new HTML body content for the page"),
      seo: z.object({
        title: z.string().optional(),
        description: z.string().optional()
      }).optional().describe("SEO information for the page"),
      published: z.boolean().optional().describe("Whether the page should be published or unpublished")
    });
  • src/index.ts:171-191 (registration)
    Registration of the 'update-page' tool in the MCP server using server.tool(), providing an inline schema and a handler that delegates to updatePage.execute().
    // Add the updatePage tool
    server.tool(
      "update-page",
      {
        pageId: z.string().min(1).describe("The GID of the page to update (e.g., \"gid://shopify/Page/1234567890\")"),
        title: z.string().optional(),
        body: z.string().optional(),
        bodyHtml: z.string().optional(),
        seo: z.object({
          title: z.string().optional(),
          description: z.string().optional()
        }).optional(),
        published: z.boolean().optional()
      },
      async (args) => {
        const result = await updatePage.execute(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result) }]
        };
      }
    );
  • src/index.ts:75-75 (registration)
    Initialization of the updatePage tool with the Shopify GraphQL client.
    updatePage.initialize(shopifyClient);
  • src/index.ts:17-17 (registration)
    Import of the updatePage tool module.
    import { updatePage } from "./tools/updatePage.js";
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