mcp-mediawiki-crunchtools

Create Page Tool

create_page_tool

Creates a new wiki page using provided title and wikitext content. Requires authentication to perform the write operation.

Instructions

Create a new wiki page. Requires authentication.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_page_tool"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Page title
`content`	Yes	Page wikitext content
`summary`	No	Edit summary (default: empty)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.1Oct 22, 2026
- addedInput schema / properties / content / description
```
Added value: +"Page wikitext content"
```
- addedInput schema / properties / summary / description
```
Added value: +"Edit summary (default: empty)"
```
- addedInput schema / properties / title / description
```
Added value: +"Page title"
```
Changed3 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / content / description
```
Removed value: -"Page wikitext content"
```
- removedInput schema / properties / summary / description
```
Removed value: -"Edit summary (default: empty)"
```
- removedInput schema / properties / title / description
```
Removed value: -"Page title"
```
Changed3 schema fields changedMay 4, 2026
- addedInput schema / properties / content / description
```
Added value: +"Page wikitext content"
```
- addedInput schema / properties / summary / description
```
Added value: +"Edit summary (default: empty)"
```
- addedInput schema / properties / title / description
```
Added value: +"Page title"
```
First observedv0.1.3Mar 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a mutation tool. It discloses the auth requirement, but says nothing about title-collision behavior (error vs overwrite), whether the edit summary is logged, required permissions, or whether the creation is immediately visible — all material for a write operation.

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 sentences with the action front-loaded and zero wasted words. The brevity is efficient, though it borders on under-specification for a mutation tool.

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

Completeness2/5

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

An output schema exists, so return values need not be described. However, for a create operation with no annotations, the description omits collision handling, permission scope, and side effects — gaps that leave an agent unable to predict behavior before writing.

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 coverage is 100%, with title, content, and summary each documented including the default. The description adds no meaning beyond that, so the baseline 3 applies; notably it does not clarify that content must be wikitext (that lives only in the schema).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a new wiki page" is a specific verb plus resource, clearly distinct from read-side siblings like get_page_tool. It never explicitly contrasts with edit_page_tool, which is the nearest alternative for existing pages, so it falls short of full sibling differentiation.

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

Usage Guidelines2/5

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

No guidance on when to use this versus edit_page_tool, or what to do if the page already exists. The only condition given is "Requires authentication," which is a prerequisite rather than a usage rule.

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