Skip to main content
Glama

Delete a comment (requires version) — leaves a tombstone

delete_comment
DestructiveIdempotent

Delete a comment (requires version) — leaves a tombstone.

The author or a project_admin may delete; an imported comment whose Jira author was not matched only a project_admin. The file stays with an empty body and deleted: true, so its seq and replies remain; the old text stays in history. Returns the tombstone.

Only when the user asked. The author or a project_admin may delete (403 not_author otherwise). Pass seq and version from list_comments. Leaves a tombstone: the body is emptied and deleted: true is set, so the seq, replies and links stay; the old text stays in history. 409 comment_deleted = already deleted.

WRITE: version must be the version from your latest read of this file (get_issue for issues, list_comments for comments, list_sprints for sprints, get_doc for project docs, read_file for md files). If the file changed since, the call fails with 409 version_conflict and the error contains the current file (details.current, details.current_version): re-read it, re-apply your change on top of the current content and retry with the new version. Never overwrite someone else's change blindly — if your change and theirs disagree, ask the user which to keep.

You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seqYesThe comment number (`seq`, as in `#c-3`).
versionYesVersion of the file you read. Required on every delete (spec principle 7).
issue_keyYesIssue key `{PROJECT}-{n}`, e.g. `KJ-101`.
project_keyYesProject key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources