Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Wiki page by id

wiki_pages_get_by_id
Read-onlyIdempotent

Fetch a Yandex Wiki page by its numeric page ID instead of slug, with optional fields, revision selection, and redirect handling.

Instructions

A single page by its numeric id — the id-based twin of pages_get/pages_get_meta.

Use it when you hold a numeric page id (e.g. from a descendants listing or a write's response) instead of the slug. fields follows the standard Wiki selector rules: without it the response carries id/slug/title only; ask for content or attributes explicitly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoExtra blocks (CSV), e.g. ``content,attributes,breadcrumbs``. Omitted = id/slug/title only.
page_idYesNumeric page id to fetch.
revision_idNoShow this past revision (an id from ``pages_revisions_list``).
raise_on_redirectNoFail if the page is a redirect instead of following it.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: the default projection (id/slug/title only) and the requirement to explicitly request content/attributes. It stops short of documenting auth needs, redirect handling (raise_on_redirect is schema-only), or error behavior, so not a full 5.

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?

Two short paragraphs, front-loaded with the identity/scope of the tool before the usage condition and the fields note. Slightly loose phrasing ('the id-based twin of') but nothing is wasted.

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 read-only single-resource getter with annotations covering safety, full schema coverage, and no output schema, the description supplies the one thing the structured fields don't fully convey: what the response contains by default and how to expand it. It is complete for correct invocation, with only edge behaviors like redirects left to the schema.

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 all four parameters are already documented, including the fields CSV format and its default. The description's 'fields follows the standard Wiki selector rules' mostly restates the schema's own explanation of the same parameter and adds no format or syntax detail beyond it, so the baseline 3 is correct.

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?

States a specific verb and resource (fetch a single wiki page) and immediately positions it as the 'id-based twin of pages_get/pages_get_meta', so the agent can distinguish it from the slug-based siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it when you hold a numeric page id ... instead of the slug' gives the exact discriminator that selects this tool over the slug-based siblings, and it even names where such an id comes from (descendants listing, write response). The alternative is implicit in 'instead of the slug' but the routing rule is unambiguous.

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