Skip to main content
Glama
Sign In
ya-tracker-mcp

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_entity_comment

Delete a comment from a Yandex Tracker project, portfolio, or goal using entity type, entity ID, and comment ID.

Instructions

Delete a comment from a project, portfolio, or goal.

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": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>",
      "comment_id": "<comment_id>"
    },
    "name": "delete_entity_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesEntity ID
comment_idYesComment ID
entity_typeYes"project", "portfolio", or "goal"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.6/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 only states 'Delete a comment' without mentioning permanence, permissions, or side effects. For a destructive operation, this lacks important context about consequences or requirements.

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. Every word contributes to meaning, making it highly concise and well-structured.

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 delete operation with three parameters and an output schema, the description adequately covers the purpose and scope. It does not need to explain return values due to the output schema, and the entity types are explicitly listed. Minor gaps exist around permissions or impact, but the tool is simple enough that the description is largely 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 baseline is 3. The description's mention of 'project, portfolio, or goal' maps to entity_type, but the schema already enumerates those values. It adds no meaningful additional semantics beyond what the schema provides.

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 (delete) and the resource (comment), with an explicit scope: 'from a project, portfolio, or goal.' This distinguishes it from the sibling delete_comment tool, which likely targets issue comments, by specifying the entity types.

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 implies the tool is for comments on projects/portfolios/goals, but it does not explicitly mention alternatives or exclusions, such as 'use delete_comment for issue comments.' It provides context but no direct guidance on when to choose this tool over related tools.

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