Skip to main content
Glama

post_qiita_article

Publish articles on Qiita with customizable options for title, content, tags, privacy, and more. Streamline content sharing using a standardized MCP tool for efficient publishing.

Instructions

create a new article on Qiita

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesMarkdown formatted content
organization_url_nameNoThe url_name of the organization for the article
privateNoWhether the article is private
slideNoWhether to enable slide mode
tagsYesList of tags for the article
titleYesArticle title
tweetNoWhether to post to Twitter

Implementation Reference

  • The main handler function for the 'post_qiita_article' tool. It uses the QiitaApiService to create a new article and returns a success or error response.
    const postQiitaArticle = async (params: PostArticleParams): Promise<any> => {
      try {
        const newItem = await apiService.createItem(params);
        
        return createSuccessResponse(
          `記事が正常に投稿されました。\nタイトル: ${newItem.title}\nURL: ${newItem.url}\n\n` + 
          JSON.stringify(newItem, null, 2)
        );
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return createErrorResponse(`Error posting Qiita article: ${errorMessage}`);
      }
    };
  • Zod schema defining the input parameters for the post_qiita_article tool, including title, body, tags, etc., and the inferred TypeScript type.
    const postArticleSchema = z.object({
      title: z.string().describe("Article title"),
      body: z.string().describe("Markdown formatted content"),
      tags: z.array(z.object({
        name: z.string().describe("Tag name"),
        versions: z.array(z.string()).optional().describe("Versions (optional)")
      })).describe("List of tags for the article"),
      private: z.boolean().optional().default(true).describe("Whether the article is private"),
      tweet: z.boolean().optional().describe("Whether to post to Twitter"),
      organization_url_name: z.string().optional().describe("The url_name of the organization for the article"),
      slide: z.boolean().optional().describe("Whether to enable slide mode")
    });
    type PostArticleParams = z.infer<typeof postArticleSchema>;
  • The registration of the 'post_qiita_article' tool within the getToolDefinitions array, specifying name, description, parameters schema, and handler.
    {
      name: "post_qiita_article",
      description: "create a new article on Qiita",
      parameters: postArticleSchema.shape,
      handler: (params: PostArticleParams) => postQiitaArticle(params)
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention authentication requirements, rate limits, whether the creation is irreversible, or what happens on success/failure. For a write operation with zero annotation coverage, this is a significant gap.

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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly, though its brevity contributes to gaps in other dimensions.

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 creation tool with no annotations and no output schema, the description is incomplete. It lacks context about authentication, error handling, return values, or how it differs from sibling tools. The high schema coverage doesn't compensate for missing behavioral and usage information.

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 the schema fully documents all 7 parameters. The description adds no parameter-specific information beyond implying creation, which doesn't enhance understanding of individual parameters. Baseline 3 is appropriate when the schema does all the work.

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 ('create') and resource ('a new article on Qiita'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_qiita_article' beyond the basic verb difference, missing explicit comparison.

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 'update_qiita_article' or 'get_my_qiita_articles'. It lacks context about prerequisites (e.g., authentication needed) or typical use cases, leaving the agent to infer usage solely from the tool name.

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

Related 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/2bo/qiita-mcp-server'

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