Skip to main content
Glama

jira_delete_worklog

Deletes a logged time entry from a Jira issue using its worklog ID, with an option to adjust the remaining time estimate after removing the logged hours.

Instructions

Remove a time entry (worklog) from a Jira issue. Get the worklog ID from jira_get_worklogs. Can optionally adjust the remaining estimate when removing the logged time.

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": {
      "issueKey": "<issueKey>",
      "worklogId": "<worklogId>"
    },
    "name": "jira_delete_worklog"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesIssue key containing the worklog (e.g., KP-123)
worklogIdYesWorklog ID to delete (get from jira_get_worklogs)
adjustEstimateNoHow to adjust remaining estimate after deletion: auto (increase by deleted time), leave (don't change)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose a side effect — that the remaining time estimate can be adjusted on deletion — but says nothing about irreversibility, required permissions, or whether the deletion is logged/auditable, which matter 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.

Conciseness5/5

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

Three short sentences with the operation stated first, the prerequisite second, and the optional side effect last. No filler or redundant restatement of the tool name.

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 destructive, three-parameter mutation with no annotations and no output schema, the description covers purpose, ID sourcing, and the estimate side effect. It leaves gaps on permissions, irreversibility, and what the call returns, which an agent must guess.

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 issueKey, worklogId, and adjustEstimate are already documented with examples and enum meanings. The description only restates the worklogId source and gestures at the estimate adjustment, adding little beyond the schema baseline.

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 uses a specific verb and resource ('Remove a time entry (worklog) from a Jira issue'), which inherently distinguishes it from the add_worklog and delete_comment siblings. It stops short of explicitly naming the sibling it contrasts with, but an agent can identify the operation unambiguously.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a concrete prerequisite workflow ('Get the worklog ID from jira_get_worklogs'), which is the main thing an agent needs before calling. It does not state exclusions or permission prerequisites (e.g., deleting another user's worklog), so it is clear context without full routing guidance.

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