Skip to main content
Glama

jira_add_worklog

Log time spent on a Jira issue using formats like 2h or 30m, and optionally adjust the remaining estimate automatically or manually.

Instructions

Log time spent working on a Jira issue. Time format examples: "2h" (2 hours), "30m" (30 minutes), "1d" (1 day), "2h 30m" (2.5 hours). Optionally adjust the remaining estimate automatically or manually.

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>",
      "timeSpent": "<timeSpent>"
    },
    "name": "jira_add_worklog"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoDescription of work performed
startedNoWhen the work was done (ISO format). Defaults to current time if not specified.
issueKeyYesIssue key to log time on (e.g., KP-123)
timeSpentYesTime spent in Jira format: "2h" (hours), "30m" (minutes), "1d" (day), "1w" (week), or combined "2h 30m"
adjustEstimateNoHow to adjust remaining estimate: auto (reduce by timeSpent), leave (don't change), new (set specific value), manual (reduce by specific amount)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

C2.9/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 behavioral burden. It discloses that the tool logs time and can optionally adjust the remaining estimate, but it does not state required permissions, whether the operation is reversible, what the response contains, or how estimate adjustment interacts with the issue's current estimate beyond a brief mention.

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?

The description is front-loaded with the core purpose, followed by brief format examples and an estimate note. It is appropriately sized, though the format examples repeat information already present in the schema and could be trimmed.

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 mutation tool with five parameters and no annotations, the description covers the core action and the optional estimate adjustment adequately for invocation. However, it omits key mutation context such as permission requirements and what a successful call returns, leaving gaps that annotations would normally fill.

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 the schema already documents all five parameters, including the adjustEstimate enum values. The description's time-format examples largely duplicate the timeSpent schema description, and it adds little semantic detail beyond what is already in the structured fields.

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 states a specific verb and resource: 'Log time spent working on a Jira issue.' This clearly distinguishes it from read-only siblings like jira_get_issue and from its direct sibling jira_delete_worklog, though it does not explicitly name any alternative.

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 prerequisites, and no explanation of when to choose this tool over alternatives such as jira_delete_worklog or jira_add_comment. The time-format examples are procedural help rather than usage routing.

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