Skip to main content
Glama
cryppadotta
by cryppadotta

create_page

Add new wiki pages to Wizzypedia by providing title and content through the MCP server.

Instructions

Create a new wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the new page
contentYesWiki content for the new page
summaryNoEdit summaryCreated via MCP

Implementation Reference

  • Core handler function in MediaWikiClient that executes the page creation by calling the MediaWiki 'edit' API with 'createonly=true'.
    async createPage(
      title: string,
      content: string,
      summary: string = ""
    ): Promise<any> {
      // Ensure we have an edit token
      const token = await this.getEditToken();
    
      return this.makeApiCall(
        {
          action: "edit",
          title,
          text: content,
          summary,
          token,
          createonly: true
        },
        "POST"
      );
    }
  • MCP server tool call handler (switch case) for 'create_page' that parses input arguments, calls the wikiClient.createPage, and formats the JSON response.
    case "create_page": {
      const {
        title,
        content,
        summary = "Created via MCP"
      } = request.params.arguments as {
        title: string;
        content: string;
        summary?: string;
      };
    
      const result = await wikiClient.createPage(title, content, summary);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                title,
                result: result.edit.result,
                newRevId: result.edit.newrevid,
                success: result.edit.result === "Success"
              },
              null,
              2
            )
          }
        ]
      };
    }
  • Input schema and metadata definition for the 'create_page' tool.
    const CREATE_PAGE_TOOL: Tool = {
      name: "create_page",
      description: "Create a new wiki page",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "Title of the new page"
          },
          content: {
            type: "string",
            description: "Wiki content for the new page"
          },
          summary: {
            type: "string",
            description: "Edit summary",
            default: "Created via MCP"
          }
        },
        required: ["title", "content"]
      }
    };
  • index.ts:598-607 (registration)
    Registers 'create_page' tool by including CREATE_PAGE_TOOL in the list returned by the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        SEARCH_PAGES_TOOL,
        READ_PAGE_TOOL,
        CREATE_PAGE_TOOL,
        UPDATE_PAGE_TOOL,
        GET_PAGE_HISTORY_TOOL,
        GET_CATEGORIES_TOOL
      ]
    }));
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write operation, it doesn't address permissions needed, whether the page becomes immediately visible, error conditions, or what happens on duplicate titles. This is inadequate for a mutation tool.

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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core purpose.

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?

For a creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation, potential side effects, or error handling. Given the complexity of creating a wiki page, more context is needed.

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 the schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high coverage.

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?

The description clearly states the action ('Create') and resource ('new wiki page'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'update_page', but it's not vague or tautological.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_page' or 'read_page'. There's no mention of prerequisites, context, or exclusions for usage.

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/cryppadotta/mcp-wizzypedia'

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