Qiita MCP Server

create_group

Create a new group for team collaboration on Qiita. Define group name, URL identifier, and privacy settings to organize team content.

Instructions

Create a new group (Qiita Team only)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "url_name": "<url_name>"
    },
    "name": "create_group"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Group display name
`url_name`	Yes	Group URL name (unique identifier)
`private`	No	Whether the group is private (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Feb 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, the description doesn't disclose important behavioral traits: whether this requires specific permissions, what happens on success/failure, whether the group becomes immediately active, or any rate limits. The 'Qiita Team only' constraint is helpful but insufficient 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 extremely concise - a single sentence that communicates the core purpose and a key constraint. It's front-loaded with the main action and wastes no words. Every part of the description earns its place.

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 explain what happens after creation, what the response contains, error conditions, or authentication requirements. The 'Qiita Team only' constraint is valuable but doesn't compensate for the missing behavioral context needed for a write operation.

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 three parameters. The description adds no additional parameter information beyond what's already in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('new group'), making the purpose immediately understandable. It also includes a platform constraint ('Qiita Team only') which adds specificity. However, it doesn't explicitly differentiate from sibling tools like 'update_group' or 'delete_group' beyond the basic verb difference.

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. It doesn't mention prerequisites (like authentication requirements), when not to use it, or how it relates to sibling tools like 'update_group' or 'list_groups'. The 'Qiita Team only' note is a platform constraint but not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server