Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Move Wiki page

wiki_pages_move

Give a wiki page a new slug by moving or renaming it; validate the request first, then poll the operation for completion.

Instructions

Move or rename pages (POST /pages/move — asynchronous; undocumented by Yandex).

The only way to give a page a new slug. The call returns a deferred operation reference — poll operations_move_get with the returned operation.id until it reaches a terminal status. A page moves with its subtree and links to the old address may stop working, so try validate_only=true first: it validates the request, applies nothing, and its operation id cannot be polled. Yandex does not document this operation (it is in the live OpenAPI only) and may change it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesMove spec: ``operations`` (each ``source`` slug and new ``target`` slug, optionally ``next_to_slug`` with ``position`` before/after) and optional ``copy_inherited_access``.
validate_onlyNoValidate the move without applying it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.122.1
    • addedInput schema / properties / body / properties / copy_inherited_access / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / body / properties / copy_inherited_access / default
      Previous value: -falseNew value: +null
    • changedInput schema / properties / body / properties / copy_inherited_access / description
      Previous value: -"Copy the accesses a page inherited from its old parent when it moves. The API refuses a move that leaves this unset (400 INHERITANCE_BEHAVIOR_IS_NOT_SPECIFIED), so it is always sent, ``false`` by default."New value: +"Copy the accesses a page inherited from its old parent when it moves. The API can refuse a move that leaves this unset (400 INHERITANCE_BEHAVIOR_IS_NOT_SPECIFIED)."
    • removedInput schema / properties / body / properties / copy_inherited_access / type
      Removed value: -"boolean"
    • removedInput schema / properties / dry_run
      Removed value: -{
-  "default": false,
-  "description": "Validate the move without applying it.",
-  "type": "boolean"
-}
    • addedInput schema / properties / validate_only
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Validate the move without applying it."
+}
  2. First observedv0.67.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare readOnly=false, destructive=false, idempotent=false, openWorld=true). The description discloses asynchrony, the deferred-operation return contract and required polling tool, subtree movement, that old links may break, the special semantics of validate_only (applies nothing, unpollable id), and that the endpoint is undocumented and unstable.

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?

Purpose and scope are front-loaded in the first two sentences, and every subsequent sentence carries distinct operational value (polling, safety, instability warning). Slightly dense at five sentences, but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description explains the return value (deferred operation reference) and the follow-up call needed to resolve it, plus the validate_only exception. For an asynchronous, undocumented mutation tool, this covers everything an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds semantics the schema lacks - notably that validate_only applies nothing and produces an id that cannot be polled. It does not help decode the copy_inherited_access 400 case beyond what the schema already states.

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 ('Move or rename pages') and immediately scopes it with 'The only way to give a page a new slug,' which distinguishes it from update/clone siblings that cannot change a slug. An agent knows exactly what this accomplishes without opening a schema.

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

Usage Guidelines4/5

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

Gives clear operating guidance: use validate_only=true first to dry-run, then poll operations_move_get. It does not explicitly name a competing sibling tool to avoid (e.g. wiki_pages_update), so it stops just short of full when/when-not/alternatives coverage.

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