Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Wiki page backlinks

wiki_pages_backlinks_list
Read-onlyIdempotent

Lists the pages that link to a given Yandex Wiki page, returning their IDs and slugs so you can trace incoming references and dependencies.

Instructions

Refs (id and slug) of the pages that link to a page (GET /pages/{id}/backlinks).

Auto-paginated. Yandex does not document this operation (it is in the live OpenAPI only) and may change it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax refs (omitted: the configured cap).
page_idYesNumeric id of the page that is linked to.
show_allNoThe API's ``show_all`` flag (undocumented; no effect seen live).
for_clusterNoLinks to the page's whole subtree, not just the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.122.1
    • addedInput schema / properties / for_cluster / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / for_cluster / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / for_cluster / type
      Removed value: -"boolean"
    • addedInput schema / properties / show_all / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / show_all / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / show_all / type
      Removed value: -"boolean"
  2. First observedv0.67.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds valuable behavioral context beyond that: it is auto-paginated and is an undocumented live-API operation that may change. It does not cover auth requirements or rate limits, but the added context is meaningful.

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?

Two short sentences with no wasted words. The return shape is front-loaded, followed by pagination behavior and the API stability caveat, which are appropriately placed.

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?

With no output schema, the description usefully states the return values (refs with id and slug), notes auto-pagination, and warns that the operation is undocumented and unstable. Combined with the annotations and fully described input schema, this is nearly complete, though it omits error or permission behavior.

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 schema already documents all four parameters well. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 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 states the specific resource (backlinks) and what is returned (refs with id and slug), plus the underlying endpoint. It clearly describes a list operation, though it does not explicitly differentiate itself from sibling wiki page listing tools.

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 gives no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It notes that the operation is undocumented and may change, which is a risk caveat rather than usage guidance.

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