yandex-wiki-search-mcp

by dlbolshov

Overview Schema Source Related Servers Discussions Admin

Python

Upload Page Attachment

page_upload_attachment

Upload a file from your local computer and attach it directly to a Yandex Wiki page using its slug or page ID.

Instructions

Upload a local file to Yandex Wiki and attach it to a page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Wiki page slug or full Wiki URL. Provide either page_id or slug.
`page_id`	No	Wiki page numeric ID. Provide either page_id or slug.
`file_path`	Yes	Local filesystem path to the file that should be uploaded.
`append_markup`	No	Whether to append Wiki file macro markup to the page after uploading the attachment.
`append_location`	No	Where to append the generated file macro when append_markup is true.	bottom

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page_id`	Yes
`attachments`	No
`appended_markup`	No
`appended_content`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv1.0.1Aug 9, 2026

removedOutput schema / $defs / WikiAttachment / additionalProperties
```
Removed value: -true
```
removedOutput schema / $defs / WikiAttachment / properties / check_status / title
```
Removed value: -"Check Status"
```
removedOutput schema / $defs / WikiAttachment / properties / created_at / title
```
Removed value: -"Created At"
```
removedOutput schema / $defs / WikiAttachment / properties / description / title
```
Removed value: -"Description"
```
removedOutput schema / $defs / WikiAttachment / properties / download_url / title
```
Removed value: -"Download Url"
```
removedOutput schema / $defs / WikiAttachment / properties / has_preview / title
```
Removed value: -"Has Preview"
```
removedOutput schema / $defs / WikiAttachment / properties / id / title
```
Removed value: -"Id"
```

addedOutput schema / $defs / WikiAttachment / properties / is_downloadable

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedOutput schema / $defs / WikiAttachment / properties / mimetype / title
```
Removed value: -"Mimetype"
```
removedOutput schema / $defs / WikiAttachment / properties / name / title
```
Removed value: -"Name"
```
removedOutput schema / $defs / WikiAttachment / properties / size / title
```
Removed value: -"Size"
```

changedOutput schema / $defs / WikiAttachment / properties / user / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/WikiUser"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / $defs / WikiAttachment / properties / user / title
```
Removed value: -"User"
```
removedOutput schema / $defs / WikiAttachment / title
```
Removed value: -"WikiAttachment"
```

addedOutput schema / $defs / WikiUser

Added value: +{
+  "description": "Trimmed user reference — the API sends much more (identity, flags…).",
+  "properties": {
+    "display_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "id": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "username": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    }
+  },
+  "type": "object"
+}

removedOutput schema / additionalProperties
```
Removed value: -true
```
removedOutput schema / properties / appended_content / title
```
Removed value: -"Appended Content"
```
removedOutput schema / properties / appended_markup / title
```
Removed value: -"Appended Markup"
```
removedOutput schema / properties / attachments / title
```
Removed value: -"Attachments"
```
removedOutput schema / properties / page_id / title
```
Removed value: -"Page Id"
```

removedOutput schema / title

Removed value: -"UploadAttachmentResult"

First observedv0.5.0Jul 19, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the tool attaches the file to a page, but does not disclose nuances like whether append_markup modifies page content or how duplicate filenames are handled. No contradictions with annotations.

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?

The description is a single, front-loaded sentence that efficiently states the tool's purpose. Every word serves a function, with no redundancy or filler.

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?

Given the full schema coverage, output schema presence, and clear annotations, the description is nearly sufficient. A slightly richer note about side effects (e.g., append_markup triggering page edits) or when to prefer this over other upload mechanisms would make it fully complete.

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 provides 100% coverage for all parameters, including descriptions for slug, page_id, file_path, append_markup, and append_location. The description itself adds no parameter-level detail, so the baseline of 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?

The description clearly states the action ('Upload a local file'), the target system ('Yandex Wiki'), and the purpose ('attach it to a page'). It distinguishes this from sibling tools like page_get_attachments (which lists attachments) and page_append_content (which appends content).

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 implies the appropriate use case: when a user needs to upload a local file and attach it to a Wiki page. It does not explicitly name alternatives or provide exclusions, but the context is clear enough to guide tool selection among siblings.

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