GitFlic MCP Server

gitflic_issue_comments_delete

DestructiveIdempotent

Deletes a comment from a GitFlic issue using the project, issue ID, and comment ID to remove outdated or unwanted discussion content.

Instructions

Delete an issue 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": {
      "project": "<project>",
      "id": "<id>",
      "commentId": "<commentId>"
    },
    "name": "gitflic_issue_comments_delete"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`raw`	No	Return the full, un-slimmed GitFlic response for THIS call (no token compression). Use when the default slim view dropped a field you need.
`project`	Yes
`commentId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no warning that deletion is permanent, no note on what happens to replies or attachments to the comment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, but for a destructive mutation it is undersized rather than appropriately concise. Nothing is wasted, yet almost nothing is said.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-record delete with an annotated destructive/idempotent profile and no output schema, the description is technically sufficient to call the tool. It is not complete enough for a destructive operation, however, since irreversibility and permission requirements are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: project, id, and commentId carry no descriptive text, and only the raw parameter is documented in the schema. The description does not compensate at all, providing no hint about the identifier formats or what project/id refer to (project slug, issue number).

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?

"Delete an issue comment" states a specific verb (delete) and a specific resource (issue comment), which cleanly separates it from siblings like gitflic_issue_delete and gitflic_issue_comments_edit. The scope is unambiguous, though the description does not name an alternative or contrast explicitly.

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?

There is no when-to-use guidance, no note about when deletion is inappropriate versus editing, and no mention of preconditions such as needing the comment author or admin rights. The agent is left to infer everything 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.

Deploy Server