Skip to main content
Glama

delete_issue_note

Removes a specific note or comment from an issue using its issue ID and note ID, helping correct or clean up issue discussions.

Instructions

Removes a specific note/comment from an issue.

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": {
      "issue_id": "<issue_id>",
      "note_id": "<note_id>"
    },
    "name": "delete_issue_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes
issue_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says nothing about whether the removal is permanent or reversible, what happens to replies/threading on the note, required permissions, or whether the deletion is soft or hard — all critical for a destructive mutation.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficiently written, though the brevity is achieved partly by omitting information an agent needs.

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 destructive two-parameter mutation with no annotations, no output schema, and no documented parameters, the definition is far too thin. It should at minimum state irreversibility, error behavior for a nonexistent note_id, and whether the note's author or admin rights are required.

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 0%, so both issue_id and note_id are undocumented in the schema. The description only implies that a note belongs to an issue; it adds no format, ID-source, or constraint information to compensate for the coverage gap.

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?

States a specific verb ("Removes") and a specific resource ("a specific note/comment from an issue"), which lets an agent distinguish it from add_issue_note and from delete_issue (which would remove the whole issue). It never names those alternatives explicitly, so differentiation comes from inference rather than the text.

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 contains no when-to-use guidance, no prerequisites, and no pointer to a sibling such as add_issue_note or delete_issue. An agent must infer the use case entirely from the verb and resource.

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