Skip to main content
Glama

update-article

Modify existing blog articles in Shopify stores by updating titles, content, summaries, tags, or author information using the article's unique identifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
articleIdYesThe GID of the article to update (e.g., "gid://shopify/Article/1234567890")
titleNo
bodyNo
summaryNo
tagsNo
authorNo

Implementation Reference

  • The main handler function that executes the GraphQL mutation to update the Shopify article using the provided input data.
    execute: async (input: UpdateArticleInput) => {
      try {
        const { articleId, ...updateData } = input;
    
        const mutation = gql`
          mutation UpdateArticle($id: ID!, $article: ArticleUpdateInput!) {
            articleUpdate(id: $id, article: $article) {
              article {
                id
                title
                handle
                body
                summary
                tags
                author {
                  name
                }
                image {
                  id
                  url
                  altText
                }
              }
              userErrors {
                field
                message
              }
            }
          }
        `;
    
        const variables = {
          id: articleId,
          article: updateData
        };
    
        const data = await shopifyClient.request(mutation, variables) as {
          articleUpdate: {
            article: {
              id: string;
              title: string;
              handle: string;
              body: string;
              summary: string;
              tags: string[];
              author: {
                name: string;
              } | null;
              image: {
                id: string;
                url: string;
                altText: string | null;
              } | null;
            };
            userErrors: Array<{
              field: string;
              message: string;
            }>;
          };
        };
    
        if (data.articleUpdate.userErrors.length > 0) {
          throw new Error(
            `Failed to update article: ${data.articleUpdate.userErrors
              .map((error) => error.message)
              .join(", ")}`
          );
        }
    
        return {
          article: data.articleUpdate.article
        };
      } catch (error) {
        console.error("Error updating article:", error);
        throw new Error(
          `Failed to update article: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
      }
    }
  • Zod input schema defining the parameters for updating an article, including articleId, title, body, summary, tags, and author.
    const UpdateArticleInputSchema = z.object({
      articleId: z.string().min(1).describe("The GID of the article to update (e.g., \"gid://shopify/Article/1234567890\")"),
      title: z.string().optional().describe("The new title for the article"),
      body: z.string().optional().describe("The new content for the article"),
      summary: z.string().optional().describe("A short summary of the article"),
      tags: z.array(z.string()).optional().describe("Tags for the article"),
      author: z.object({
        name: z.string()
      }).optional().describe("Author information for the article")
    });
  • src/index.ts:242-261 (registration)
    Registers the 'update-article' tool with the MCP server, providing an inline Zod schema and a handler that delegates to the imported updateArticle.execute method.
    // Add the updateArticle tool
    server.tool(
      "update-article",
      {
        articleId: z.string().min(1).describe("The GID of the article to update (e.g., \"gid://shopify/Article/1234567890\")"),
        title: z.string().optional(),
        body: z.string().optional(),
        summary: z.string().optional(),
        tags: z.array(z.string()).optional(),
        author: z.object({
          name: z.string()
        }).optional()
      },
      async (args) => {
        const result = await updateArticle.execute(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result) }]
        };
      }
    );
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