Yandex Tracker MCP

Overview Schema Source Related Servers Discussions Admin

Update Worklog

issue_update_worklog

Update an existing worklog entry in a Yandex Tracker issue by specifying issue ID and worklog ID, with optional new start time, duration, or comment.

Instructions

Update a worklog entry (spent time record) in a Yandex Tracker 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": {
      "issue_id": "<issue_id>",
      "worklog_id": "<worklog_id>"
    },
    "name": "issue_update_worklog"
  }
}

Input Schema

Name	Required	Description
`start`	No	New start datetime for the worklog. If timezone is not provided, UTC is assumed.
`comment`	No	New comment for the worklog entry.
`duration`	No	New time spent in ISO-8601 duration format (e.g., 'PT1H30M').
`issue_id`	Yes	Issue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
`worklog_id`	Yes	Worklog entry ID (integer).

Output Schema

Name	Required	Description	Default
`id`	Yes
`issue`	No
`start`	No
`comment`	No
`duration`	No
`createdAt`	No
`createdBy`	No
`updatedAt`	No
`updatedBy`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.6.3May 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations set readOnlyHint to false, confirming this is a write operation. The description adds no further behavioral context, such as whether fields are overwritten or merged, or any side effects. With annotations covering the read/write nature, the description provides minimal additional transparency.

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 a single short sentence with no wasted words. It is appropriately concise for its purpose, though it could be slightly more informative without sacrificing brevity.

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?

Given the tool has 5 parameters and an output schema (not shown), the description lacks information about return values, partial updates, or error conditions. It is minimally adequate for a simple update tool but leaves room for more context.

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 each parameter is already documented. The description adds 'spent time record' context but no parameter-specific details beyond the schema. Baseline score of 3 is appropriate.

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 clearly states the verb 'Update' and the resource 'worklog entry (spent time record)' in Yandex Tracker. It distinguishes from siblings by specifying 'update' rather than 'add' or 'delete', but does not explicitly differentiate from other update tools like issue_update.

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 provides no guidance on when to use this tool versus alternatives such as issue_add_worklog or issue_delete_worklog. An agent would need to infer usage from the name alone.

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

Deploy Server