Skip to main content
Glama
Selenium39

Qiita API MCP Server

create_item

Create and publish articles on Qiita, a Japanese developer community platform. Write content in Markdown, add tags, and control visibility settings.

Instructions

新しい記事を作成します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes記事のタイトル
bodyYes記事の本文(Markdown形式)
tagsYesタグの配列
privateNo非公開記事かどうか
tweetNoTwitterに投稿するかどうか

Implementation Reference

  • Handler definition for the 'create_item' tool, which delegates execution to the QiitaApiClient's createItem method.
    create_item: {
      schema: createItemSchema,
      execute: async (input, client) => client.createItem(input),
  • Zod schemas defining the input validation for the create_item tool, including tag specification.
    const tagSpecificationSchema = z.object({
      name: z.string(),
      versions: z.array(z.string()),
    });
    
    const createItemSchema = z.object({
      title: z.string(),
      body: z.string(),
      tags: z.array(tagSpecificationSchema),
      private: z.boolean().default(false),
      tweet: z.boolean().default(false),
    });
  • MCP tool registration for 'create_item', providing the tool name, description, and JSON input schema used by the MCP server.
    {
      name: 'create_item',
      description: '新しい記事を作成します',
      inputSchema: {
        type: 'object',
        properties: {
          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,
          },
          tweet: {
            type: 'boolean',
            description: 'Twitterに投稿するかどうか',
            default: false,
          },
        },
        required: ['title', 'body', 'tags'],
      },
    },
  • The Qiita API client method that performs the actual HTTP POST request to create an item on Qiita.
    async createItem(item: {
      title: string;
      body: string;
      tags: Array<{ name: string; versions: string[] }>;
      private?: boolean;
      tweet?: boolean;
    }) {
      this.assertAuthenticated();
      const response = await this.client.post('/items', item);
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'creates' which implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether creation is idempotent, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 in Japanese that directly states the tool's purpose. There's zero wasted language or unnecessary elaboration. It's appropriately sized and front-loaded with the essential information.

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 (create operation) with no annotations and no output schema, the description is incomplete. It doesn't address what happens after creation (e.g., returns the created item ID), error conditions, authentication requirements, or side effects like the tweet parameter's Twitter posting. The agent lacks crucial context for proper tool invocation.

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?

Schema description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional meaning about parameters beyond implying article creation. It doesn't explain parameter relationships, constraints, or usage examples. With high schema coverage, baseline 3 is appropriate when description doesn't enhance parameter understanding.

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 '新しい記事を作成します' (creates a new article) clearly states the verb (create) and resource (article). It distinguishes from siblings like update_item, delete_item, and get_item by specifying creation rather than modification, retrieval, or deletion. However, it doesn't explicitly differentiate from create_comment, which creates a different resource type.

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. There's no mention of prerequisites (e.g., authentication), when not to use it, or explicit alternatives like update_item for modifying existing articles. The agent must infer usage from the tool name alone.

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