Skip to main content
Glama
Selenium39

Qiita API MCP Server

update_item

Modify existing Qiita articles by updating titles, content, tags, or visibility settings using article ID.

Instructions

既存の記事を更新します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes記事ID
titleYes記事のタイトル
bodyYes記事の本文(Markdown形式)
tagsYesタグの配列
privateNo非公開記事かどうか

Implementation Reference

  • The execution handler for the 'update_item' MCP tool, which destructures itemId from input and forwards the remaining fields as update data to the QiitaApiClient's updateItem method.
    update_item: {
      schema: updateItemSchema,
      execute: async ({ itemId, ...rest }, client) => client.updateItem(itemId, rest),
    },
  • Zod schema used for runtime input validation of the update_item tool handler.
    const updateItemSchema = z.object({
      itemId: z.string(),
      title: z.string(),
      body: z.string(),
      tags: z.array(tagSpecificationSchema),
      private: z.boolean().optional(),
    });
  • MCP Tool definition object for 'update_item', including name, description, and JSON inputSchema used for tool listing and validation.
    {
      name: 'update_item',
      description: '既存の記事を更新します',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: {
            type: 'string',
            description: '記事ID',
          },
          title: {
            type: 'string',
            description: '記事のタイトル',
          },
          body: {
            type: 'string',
            description: '記事の本文(Markdown形式)',
          },
          tags: {
            type: 'array',
            description: 'タグの配列',
            items: {
              type: 'object',
              properties: {
                name: {
                  type: 'string',
                  description: 'タグ名',
                },
                versions: {
                  type: 'array',
                  description: 'タグのバージョン',
                  items: {
                    type: 'string',
                  },
                },
              },
              required: ['name', 'versions'],
            },
          },
          private: {
            type: 'boolean',
            description: '非公開記事かどうか',
            default: false,
          },
        },
        required: ['itemId', 'title', 'body', 'tags'],
      },
    },
  • Low-level API client method that sends a PATCH request to Qiita's /items/{itemId} endpoint to update the item, called by the tool handler.
    async updateItem(itemId: string, item: {
      title: string;
      body: string;
      tags: Array<{ name: string; versions: string[] }>;
      private?: boolean;
    }) {
      this.assertAuthenticated();
      const response = await this.client.patch(`/items/${itemId}`, item);
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. While 'update' implies a mutation operation, the description doesn't mention permission requirements, whether the update is reversible, what happens to unspecified fields, rate limits, or error conditions. This leaves significant behavioral gaps for a mutation tool.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a straightforward update operation and gets directly to the point with zero wasted content.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address behavioral aspects like permissions, side effects, or error handling, nor does it explain what the tool returns. The agent would need to guess about important operational details.

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

Parameters3/5

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

The input schema has 100% description coverage, providing clear documentation for all 5 parameters. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline expectation without adding extra value. This is adequate but not exceptional.

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 ('update') and target resource ('existing article'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update_comment' or explain what distinguishes article updates from comment updates, which prevents a perfect score.

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 like 'create_item' or 'update_comment'. It doesn't mention prerequisites (e.g., needing an existing itemId), appropriate contexts, or when other tools might be more suitable, leaving the agent with insufficient usage context.

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/Selenium39/mcp-server-qiita'

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