Skip to main content
Glama
cryppadotta
by cryppadotta

update_page

Modify existing wiki page content on Wizzypedia by providing new text and an optional edit summary.

Instructions

Update an existing wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the page to update
contentYesNew wiki content for the page
summaryNoEdit summaryUpdated via MCP

Implementation Reference

  • MCP tool handler for 'update_page': extracts parameters from tool call arguments, invokes wikiClient.updatePage, and returns structured JSON response with edit result.
    case "update_page": {
      const {
        title,
        content,
        summary = "Updated via MCP"
      } = request.params.arguments as {
        title: string;
        content: string;
        summary?: string;
      };
    
      const result = await wikiClient.updatePage(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
            )
          }
        ]
      };
    }
  • MediaWikiClient method that performs the actual MediaWiki API 'edit' action to update page content, handling edit token acquisition.
    async updatePage(
      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
        },
        "POST"
      );
    }
  • Tool schema definition specifying input parameters (title, content, optional summary) for the update_page tool.
    const UPDATE_PAGE_TOOL: Tool = {
      name: "update_page",
      description: "Update an existing wiki page",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "Title of the page to update"
          },
          content: {
            type: "string",
            description: "New wiki content for the page"
          },
          summary: {
            type: "string",
            description: "Edit summary",
            default: "Updated via MCP"
          }
        },
        required: ["title", "content"]
      }
    };
  • index.ts:598-607 (registration)
    Registration of all tools including UPDATE_PAGE_TOOL in the ListTools handler, making the tool discoverable by MCP clients.
    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. 'Update' implies a mutation operation, but the description doesn't specify permissions required, whether changes are reversible, rate limits, or what happens if the page doesn't exist. This leaves significant behavioral gaps 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.

Conciseness5/5

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

The description is a single, clear sentence with zero wasted words. It's front-loaded with the essential information (update + wiki page) and doesn't include unnecessary elaboration or repetition.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, or behavioral constraints. Given the complexity of updating a wiki page (which could involve permissions, versioning, etc.), 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 all parameters are documented in the schema. The description doesn't add any parameter-specific information beyond what the schema already provides (title, content, summary). This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Update') and resource ('an existing wiki page'), making the purpose immediately understandable. It distinguishes from siblings like 'create_page' (new vs existing) and 'read_page' (read vs update), though it doesn't explicitly mention these distinctions in the text itself.

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 'create_page' for new pages or 'read_page' for viewing. It doesn't mention prerequisites (e.g., page must exist) or contextual considerations, leaving the agent to infer usage from the tool name alone.

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