Yandex Tracker MCP

Overview Schema Source Related Servers Discussions Admin

Add Worklog

issue_add_worklog

Add a worklog entry to a Yandex Tracker issue by specifying duration and optional comment and start time to track time spent.

Instructions

Add a worklog entry (log spent time) to 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>",
      "duration": "<duration>"
    },
    "name": "issue_add_worklog"
  }
}

Input Schema

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

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

A3.6/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=false, so the description's mention of 'Add' aligns. However, no additional behavioral traits are disclosed (e.g., permissions needed, side effects like triggering notifications, or rate limits). The description adds minimal value beyond annotations.

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?

A single, direct sentence with no wasted words. It is appropriately front-loaded and provides essential information efficiently.

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?

Given the 100% schema coverage and existence of an output schema, the description is fairly complete. It lacks mention of error conditions or prerequisites (e.g., issue must exist), but for a straightforward add operation, it is adequate.

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?

All four parameters are described in the input schema (100% coverage). The description does not add new meaning beyond the schema; it merely restates the tool's purpose. Baseline of 3 is appropriate given high schema coverage.

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 clearly states the action ('Add a worklog entry'), the resource ('worklog entry'), and the context ('to a Yandex Tracker issue'). It effectively distinguishes from sibling tools like issue_delete_worklog, issue_update_worklog, and issue_get_worklogs.

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 description provides no explicit guidance on when to use this tool versus alternatives (e.g., issue_add_comment). It only describes the function without usage context or prerequisites, leaving the agent to infer based on the tool name.

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

Deploy Server