Skip to main content
Glama
Sign In
atlassian-browser-mcp

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Worklog

jira_add_worklog
Destructive

Add a worklog entry to a Jira issue with time spent, optional comment, start time, and estimate updates.

Instructions

Add a worklog entry to a Jira issue.

Input Schema

NameRequiredDescriptionDefault
commentNo(Optional) Comment for the worklog in Markdown format
startedNo(Optional) Start time in ISO format. If not provided, the current time will be used. Example: '2023-08-01T12:00:00.000+0000'
issue_keyYesJira issue key (e.g., 'PROJ-123', 'ACV2-642')
time_spentYesTime spent in Jira format. Examples: '1h 30m' (1 hour and 30 minutes), '1d' (1 day), '30m' (30 minutes), '4h' (4 hours)
original_estimateNo(Optional) New value for the original estimate
remaining_estimateNo(Optional) New value for the remaining estimate

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / issue_key / pattern
      Previous value: -"^[A-Z][A-Z0-9_]+-\\d+$"New value: +"^[A-Z][A-Z0-9_]+-\\d+(?:-\\d+)*$"
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Addedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds no further behavioral context, such as permission requirements, whether time entries can be edited or removed, or how it affects issue estimates.

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 front-loaded sentence with no filler or repetition. It is appropriately sized for a tool whose parameters and safety profile are already documented elsewhere.

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?

The rich input schema, output schema, and annotations cover invocation details and safety hints. However, the description omits usage context that would help an agent choose between adding a worklog and related actions like commenting or reading worklogs.

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 all six parameters are already documented with formats and examples. The description adds no parameter meaning beyond what the schema provides, which is the baseline expectation at this coverage level.

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: adding a worklog entry to a Jira issue. It is clearly distinct from the read-only sibling jira_get_worklog, but it does not explicitly differentiate itself from related mutation tools such as jira_add_comment.

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 on when to use this tool, what prerequisites exist, or how it relates to alternatives like jira_get_worklog or jira_add_comment. Usage is only implied by the tool name and description.

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

Deploy Server

Other Tools