Skip to main content
Glama

jira_get_worklogs

Retrieve all time tracking entries for a Jira issue, including who logged time, hours, dates, and descriptions, for time reporting, billing, or effort analysis.

Instructions

Retrieve all time tracking entries (worklogs) for a Jira issue. Shows who logged time, how much, when, and optional work descriptions. Useful for time reporting, billing, or understanding effort spent on 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": {
      "issueKey": "<issueKey>"
    },
    "name": "jira_get_worklogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
startAtNoStarting index for pagination
issueKeyYesIssue key to get time entries for (e.g., KP-123)
maxResultsNoMaximum number of worklogs to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.6/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 burden; it does disclose the returned content (user, duration, timestamp, optional descriptions), which is real behavioral info. However it never mentions that results are paginated or that maxResults defaults to 50 with a 100 cap, nor anything about permissions or empty-result behavior for issues with no worklogs.

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?

Two sentences, no redundancy, and the core operation plus target resource is stated in the very first clause. The follow-up sentence earns its place by describing payload and use cases rather than restating the name.

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

Completeness4/5

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

For a simple read-only, three-parameter tool with full schema coverage and no output schema, the definition covers what the tool returns and why it matters. The only shortfall is silence on pagination semantics at the tool level, which the agent must infer from the parameter descriptions.

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%, with startAt, maxResults, and issueKey each documented including formats and bounds, so the schema does the heavy lifting. The description adds nothing parameter-specific beyond noting 'optional work descriptions' on the output side, which is consistent with the baseline 3.

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 and resource ('Retrieve all time tracking entries (worklogs)') scoped to a Jira issue, and the second sentence enumerates the returned fields (who, how much, when, descriptions). It does not explicitly contrast itself with jira_add_worklog or jira_delete_worklog, but 'retrieve' versus add/delete is unambiguous, so an agent can separate it from those siblings.

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

Usage Guidelines3/5

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

The 'Useful for time reporting, billing, or understanding effort spent on an issue' clause supplies use-case context but is framed as why the data matters rather than a directive on when to call this versus alternatives. There is no mention of prerequisites (issue key validity, permissions) or any when-not condition.

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