Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Tracker entity links

tracker_entities_links_list
Read-onlyIdempotent

List an entity's links to other Yandex Tracker entities, including link type and linked entity summary and ID. Provide entity type and ID to inspect relationships.

Instructions

An entity's links to other entities — the link type and the linked entity's summary + id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include in the reply.
entity_idYesEntity id (or shortId).
entity_typeYesEntity type: ``project``, ``portfolio`` or ``goal``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.122.1
    • addedInput schema / properties / fields
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Comma-separated fields to include in the reply."
+}
  2. First observedv0.67.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds the return shape (link type + summary/id) but says nothing about pagination, permissions, or volume limits, so it clears the lowered bar without being rich.

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?

A single em-dash sentence with no filler, and the core content is front-loaded. It is perhaps terse to the point of under-specification, but every word earns its place.

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?

For a simple read tool whose annotations carry the safety profile, the essentials are present, and the description helpfully compensates for the absence of an output schema by naming the returned fields. It still omits pagination and how the optional 'fields' parameter interacts with the reply, which leaves a gap for a list tool.

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%: entity_id, entity_type (with its allowed values) and the fields comma-separated list are all documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 names the resource (an entity's links to other entities) and specifies the payload the tool surfaces (link type plus the linked entity's summary and id), so an agent knows what it gets back. It does not, however, distinguish itself from the sibling link tools (tracker_entities_links_create/delete, tracker_links_list*), leaving that differentiation to the name.

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 when-to-use statement, no prerequisites, and no mention of alternatives such as tracker_links_list or tracker_links_list_filtered. The agent must infer that this is read-only by 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

Other Tools