jira-mcp-server

add_worklog

Log time worked on a Jira issue by providing the issue key and duration. Add optional comments and start time for accurate tracking.

Instructions

Add a worklog to an issue (log hours worked)

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": "add_worklog"
  }
}

Input Schema

Name	Required	Description
`comment`	No	Optional comment for the worklog
`started`	No	ISO 8601 date time (optional)
`issueKey`	Yes	Issue key (e.g., PROJ-123)
`timeSpent`	Yes	Time spent (e.g., '2h 30m')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation but does not state whether it requires write permissions, whether it appends to the issue history, or what the response contains. The absence of any side-effect or prerequisite information is a significant gap for a mutation tool.

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?

The description is a single, clear sentence with no extraneous words. Every word adds value, and the parenthetical clarifies the purpose.

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

Completeness2/5

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

The tool is a simple mutation with no output schema and no annotations. The description does not mention return values, error conditions, or permission requirements. Given the lack of structured context, a more detailed description is needed to be complete.

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 four parameters. The description adds no additional meaning beyond the schema, except for the general context of logging hours. This meets the baseline for a tool where schema does the heavy lifting.

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

Purpose5/5

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

The description uses a specific verb ('Add') and resource ('worklog') with context ('to an issue') and clarifies the action as logging hours worked. This clearly distinguishes it from sibling tools like update_worklog and delete_worklog.

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?

The description only states what the tool does but gives no guidance on when to use it versus alternatives. It does not mention that this is for creating new worklogs and not for editing or deleting them, nor does it reference any sibling tools.

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