Qiita MCP Server

update_template

Modify an existing template's title, body, or tags for Qiita Team users to maintain consistent documentation standards.

Instructions

Update an existing template (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": {
      "template_id": "<template_id>"
    },
    "name": "update_template"
  }
}

Input Schema

Name	Required	Description
`template_id`	Yes	Template ID to update
`title`	No	New template title
`body`	No	New template body in Markdown
`tags`	No	New tags (array of {name, versions?})

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 full burden for behavioral disclosure. While 'Update' implies a mutation operation, the description doesn't specify permission requirements, whether changes are reversible, what happens to existing template fields not mentioned, or any rate limits. The 'Qiita Team only' hint 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 with no wasted words. It's front-loaded with the core action and includes the important 'Qiita Team only' qualification efficiently. Every word serves a purpose.

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 inadequate. It doesn't explain what the tool returns, error conditions, or behavioral details needed for safe invocation. The 'Qiita Team only' constraint is useful but doesn't compensate for missing critical information about 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?

Schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete, but doesn't provide extra value.

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 resource ('an existing template'), making the purpose understandable. It specifies 'Qiita Team only' which adds useful context, though it doesn't explicitly differentiate from sibling tools like 'create_template' or 'delete_template' beyond the update action.

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 minimal guidance - only mentioning 'Qiita Team only' as a constraint. It doesn't indicate when to use this tool versus alternatives like 'create_template' or 'expand_template', nor does it mention prerequisites or typical use cases for template updates.

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

Deploy Server