Jira Cloud MCP Server

delete_worklog

Remove a worklog entry from a Jira issue. Provide the issue key and worklog ID to delete it, with options to adjust the remaining estimate or notify watchers.

Instructions

Delete worklog

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": {
      "issueIdOrKey": "<issueIdOrKey>",
      "id": "<id>"
    },
    "name": "delete_worklog"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The ID of the worklog.
`increaseBy`	No	The amount to increase the issue's remaining estimate by, as days (\#d), hours (\#h), or minutes (\#m or \#). For exampl
`newEstimate`	No	The value to set as the issue's remaining time estimate, as days (\#d), hours (\#h), or minutes (\#m or \#). For example
`notifyUsers`	No	Whether users watching the issue are notified by email.
`issueIdOrKey`	Yes	The ID or key of the issue.
`adjustEstimate`	No	Defines how to update the issue's time estimate, the options are: * `new` Sets the estimate to a specific value, defi	auto
`overrideEditableFlag`	No	Whether the work log entry should be added to the issue even if the issue is not editable, because jira.issue.editable s

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

C2.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool deletes a worklog, without mentioning whether the deletion is permanent, how it affects issue time estimates, notifications, or any other side effects.

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

Conciseness2/5

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

The description is extremely short but under-specified rather than genuinely concise. It has no structured content, no sentence that earns its place beyond restating the tool name, and omits important context that could be conveyed in minimal additional text.

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

Completeness1/5

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

For a destructive operation with seven parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain required inputs, behavior, return value, or side effects, leaving an agent without enough information to invoke the tool correctly and confidently.

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%, and the schema already documents all seven parameters. The description adds no parameter-level meaning, but since the schema carries the burden, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete worklog' is a direct restatement of the tool name delete_worklog. It names the action and resource but adds no additional specificity about scope, target, or effect, so it qualifies as a tautology rather than a substantive purpose statement.

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 guidance about when to use this tool versus alternatives. Sibling tools such as update_worklog, add_worklog, and get_worklog exist, but the description does not clarify when deletion is appropriate or how it differs from these related operations.

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

Deploy Server