Skip to main content
Glama
Olson3R
by Olson3R

update_page

Modify and refresh Confluence pages by updating their title, content, and version number through the MCP server, ensuring accurate and synchronized page revisions.

Instructions

Update an existing Confluence page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesNew page content
pageIdYesPage ID to update
titleYesNew page title
versionYesCurrent version number (required for updates)

Implementation Reference

  • Core implementation of page update logic: fetches current page for validation, constructs UpdatePageRequest, and performs PUT request to Confluence API
    async updatePage(
      pageId: string, 
      title: string, 
      content: string, 
      version: number
    ): Promise<ConfluencePage> {
      const currentPage = await this.getPage(pageId);
      
      if (!currentPage.space || !currentPage.space.key) {
        throw new Error('Unable to determine page space for access validation');
      }
      
      if (!validateSpaceAccess(currentPage.space.key, this.config.allowedSpaces)) {
        throw new Error(`Access denied to space: ${currentPage.space.key}`);
      }
    
      const updateData: UpdatePageRequest = {
        id: pageId,
        status: 'current',
        title,
        type: 'page',
        version: { number: version },
        body: {
          storage: {
            value: content,
            representation: 'storage'
          }
        }
      };
    
      const response: AxiosResponse<ConfluencePage> = await this.client.put(`/pages/${pageId}`, updateData);
      return response.data;
    }
  • MCP server tool handler for 'update_page': extracts parameters from request and calls ConfluenceClient.updatePage
    case 'update_page': {
      const { pageId, title, content, version } = args as {
        pageId: string;
        title: string;
        content: string;
        version: number;
      };
      
      const page = await confluenceClient.updatePage(pageId, title, content, version);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(page, null, 2)
          }
        ]
      };
    }
  • src/index.ts:115-139 (registration)
    Tool registration in ListTools handler, including name, description, and input schema
      name: 'update_page',
      description: 'Update an existing Confluence page',
      inputSchema: {
        type: 'object',
        properties: {
          pageId: {
            type: 'string',
            description: 'Page ID to update'
          },
          title: {
            type: 'string',
            description: 'New page title'
          },
          content: {
            type: 'string',
            description: 'New page content'
          },
          version: {
            type: 'number',
            description: 'Current version number (required for updates)'
          }
        },
        required: ['pageId', 'title', 'content', 'version']
      }
    },
  • TypeScript interface defining the structure of data sent to Confluence update API
    export interface UpdatePageRequest {
      id: string;
      status: string;
      title: string;
      type: string;
      version: {
        number: number;
      };
      body: {
        storage: {
          value: string;
          representation: string;
        };
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation operation, it doesn't specify permission requirements, whether changes are reversible, rate limits, or what happens to existing content not mentioned. For a mutation tool with zero annotation coverage, this is a significant gap.

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 that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 update operation entails (e.g., overwriting vs. merging), potential side effects, error conditions, or return values. Given the complexity and lack of structured data, 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?

The schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema (e.g., format details, examples, or constraints). This meets the baseline for high schema 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 verb ('Update') and resource ('an existing Confluence page'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'move_page' or 'create_page' beyond the basic operation name, which prevents a perfect score.

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' or 'move_page'. It doesn't mention prerequisites (e.g., needing an existing page ID) or contextual constraints, 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

Related 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/Olson3R/confluence-mcp'

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