Skip to main content
Glama

Append Wiki Content

page_append_content

Append markdown content to a Yandex Wiki page—at the top, bottom, or a specific anchor—by providing the page slug or ID.

Instructions

Append content to the top, bottom, or anchor of a Yandex Wiki page. Content is Markdown (YFM): plain Markdown renders as-is, but GitHub-specific extensions ('[!NOTE]' alerts, raw HTML) do not — see the wiki-mcp://yfm-cheatsheet resource for YFM equivalents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoWiki page slug or full Wiki URL. Provide either page_id or slug.
anchorNoAnchor name like '#release-notes'. Overrides location when provided.
contentYesContent block to append.
page_idNoWiki page numeric ID. Provide either page_id or slug.
locationNoTarget location in the page body when anchor is not provided.bottom

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
slugNo
ownerNo
titleNo
contentNo
redirectNo
page_typeNo
attributesNo
created_atNo
breadcrumbsNo
modified_atNo
access_listsNo
yfm_warningsNoMarkup warnings for the submitted content (the write itself succeeded): parts that will not render as intended on Yandex Wiki. See the wiki-mcp://yfm-cheatsheet resource for fixes.
access_policyNo
Behavior4/5

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

Annotations (openWorldHint=false, destructiveHint=false) already indicate a non-destructive, closed operation. The description goes beyond annotations by explaining Markdown/YFM limitations and pointing to the wiki-mcp://yfm-cheatsheet resource, which is valuable behavioral context. It does not cover permissions or failure modes, but that is not required given the annotation coverage.

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 sentences, front-loaded with primary purpose, and every sentence adds value. No fluff or repetition of schema/annotation content.

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?

The tool has an output schema and a rich input schema covering all parameters. The description supplies the essential extra context (YFM format constraints and pointer to cheatsheet) needed to use the tool correctly, making it complete for this context.

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?

The input schema has 100% description coverage for all 5 parameters, so the schema does the heavy lifting. The description mentions 'top, bottom, or anchor' which aligns with the location and anchor parameters, but it does not add extra semantic detail 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?

The description clearly states the verb 'append' and the resource 'Yandex Wiki page', and specifies three target locations (top, bottom, anchor). This distinguishes it from sibling tools like page_update or page_create, which have different operations.

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?

The description clearly implies this tool is for appending content to existing pages, with location choices, but it does not explicitly mention when not to use it or present alternatives. The context is clear enough for an agent to select it over page_update when only appending is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dlbolshov/yandex-wiki-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server