Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Clone Wiki page

wiki_pages_clone

Copies an existing Wiki page to a new address (slug) asynchronously, returning an operation ID for status polling.

Instructions

Copy a page to a new address (POST /pages/{id}/clone — asynchronous).

Cloning leaves the original where it is; to give the page itself a new slug use pages_move. The call returns a deferred operation reference — poll operations_clone_get with the returned operation.id until it reaches a terminal status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesClone spec: required ``target`` (destination slug) plus optional ``title`` and ``subscribe_me``.
page_idYesNumeric id of the page to copy.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety/write profile is covered structurally. On top of that the description discloses the async nature ('asynchronous'), that a deferred operation is returned requiring polling, and that the source page is left intact. It does not mention permission requirements or what happens to subscriptions, hence 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.

Conciseness5/5

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

Three tight sentences with zero filler, and the core behavior ('copy a page') is front-loaded before the alternative and the follow-up polling step. Each sentence carries distinct, load-bearing information.

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?

For an asynchronous 2-parameter tool with no output schema, the description supplies exactly what is missing from structured data: the async return shape, the polling tool, and the terminal-status condition. Nothing needed to invoke and follow through the call is absent.

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 both page_id and the nested body fields (target, title, subscribe_me) are already fully documented in the schema. The description adds no extra parameter-level meaning beyond referencing the returned operation.id. Baseline 3 is appropriate.

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 ('Copy a page to a new address') and immediately frames the endpoint. It explicitly distinguishes itself from the sibling pages_move, which is the only neighboring operation an agent could confuse it with.

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?

Explicitly says when to use an alternative ('to give the page itself a new slug use pages_move'), and it removes the calling ambiguity created by the async return value by naming the follow-up tool (operations_clone_get) and the exact key to poll (operation.id). Both the when-to-use and the when-to-use-something-else cases are covered.

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