Skip to main content
Glama
Sign In
Qiita MCP Server

Qiita MCP Server

by sunu-py-jp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_comment

Modify an existing comment on Qiita by providing the comment ID and updated Markdown content to edit or correct previously posted comments.

Instructions

Update an existing comment

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": {
      "comment_id": "<comment_id>",
      "body": "<body>"
    },
    "name": "update_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesThe ID of the comment
bodyYesThe updated comment body in Markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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. It states it's an update operation but doesn't mention permissions required, whether changes are reversible, rate limits, error conditions, or what happens to other comment fields not mentioned. This leaves significant 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 gets straight to the point with zero wasted words. It's appropriately sized for a simple update operation and front-loads 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 with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns, error conditions, permissions needed, or behavioral constraints. The 100% schema coverage helps with parameters, but overall context for safe and effective use is missing.

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 both parameters thoroughly. The description doesn't add any additional meaning about the parameters beyond what's in the schema descriptions, so it meets the baseline for high schema coverage without compensating 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 verb ('update') and resource ('an existing comment'), making the purpose immediately understandable. It distinguishes from sibling tools like 'create_comment' and 'delete_comment' by specifying it's for existing comments, though it doesn't explicitly contrast with other update tools like 'update_group' or 'update_item'.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing the comment ID), when not to use it, or how it differs from similar tools like 'create_comment' or 'import_comment' beyond the basic verb difference.

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

Deploy Server

Other Tools