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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bulk_update_entities

Update multiple projects, portfolios, or goals simultaneously using a list of entity IDs, with an optional comment.

Instructions

Bulk update multiple entities.

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_ids": "<entity_ids>"
    },
    "name": "bulk_update_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional comment
entity_idsYesList of entity IDs
entity_typeYes"project", "portfolio", or "goal"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

C2/5.0
Behavior1/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, but it only states that the tool updates entities in bulk. It does not mention potential destructive effects, whether the operation is atomic, error handling for partial failures, or any permissions required, leaving the agent completely in the dark about side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-sentence description is concise but severely under-specified, similar to a placeholder. It does not earn its place because it provides no useful information beyond the tool name, making it more of a tautology than a helpful, content-rich description.

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?

For a bulk mutation tool with 3 parameters, no annotations, and no explanation of update semantics (which fields are modified, what happens on failure), the description is inadequate. The existence of an output schema reduces the need to describe return values, but the lack of behavioral and usage context makes the tool difficult to invoke correctly.

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?

The input schema fully documents the parameters: entity_type, entity_ids, and comment, with 100% coverage. The description adds no additional semantic context beyond the schema, so it neither helps nor hinders. Since schema coverage is high, the baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'Bulk update multiple entities' essentially restates the tool name 'bulk_update_entities' without adding specificity. It does not mention that it updates projects, portfolios, or goals, nor does it distinguish this tool from sibling bulk operations like 'bulk_update' or 'bulk_move', making it a near-tautology.

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 versus alternatives such as 'update_entity' for single updates or 'bulk_update' for issues. The description does not provide any context, prerequisites, or exclusions, leaving the agent to guess the appropriate use case.

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