Skip to main content
Glama
Olson3R
by Olson3R

move_page

Relocate a Confluence page to a different space or parent page by specifying the page ID, target space key, and optional parent ID. Simplify content organization on the Confluence MCP Server.

Instructions

Move a Confluence page to a different space or parent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYesPage ID to move
parentIdNoOptional: New parent page ID in the target space
targetSpaceKeyYesTarget space key to move the page to

Implementation Reference

  • Core handler function that executes the page move logic: validates access to source and target spaces, fetches current page, constructs MovePageRequest, and performs PUT /pages/{pageId} to move the page.
    async movePage(
      pageId: string,
      targetSpaceKey: string,
      parentId?: string
    ): 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 source space: ${currentPage.space.key}`);
      }
      
      if (!validateSpaceAccess(targetSpaceKey, this.config.allowedSpaces)) {
        throw new Error(`Access denied to target space: ${targetSpaceKey}`);
      }
    
      const moveData: MovePageRequest = {
        version: { number: currentPage.version.number },
        title: currentPage.title,
        type: 'page',
        space: { key: targetSpaceKey }
      };
    
      if (parentId) {
        moveData.ancestors = [{ id: parentId }];
      }
    
      const response: AxiosResponse<ConfluencePage> = await this.client.put(`/pages/${pageId}`, moveData);
      return response.data;
    }
  • MCP tool schema registration including name, description, and input schema for move_page.
    {
      name: 'move_page',
      description: 'Move a Confluence page to a different space or parent',
      inputSchema: {
        type: 'object',
        properties: {
          pageId: {
            type: 'string',
            description: 'Page ID to move'
          },
          targetSpaceKey: {
            type: 'string',
            description: 'Target space key to move the page to'
          },
          parentId: {
            type: 'string',
            description: 'Optional: New parent page ID in the target space'
          }
        },
        required: ['pageId', 'targetSpaceKey']
      }
    },
  • MCP CallToolRequestSchema dispatch handler for move_page: extracts arguments and delegates to ConfluenceClient.movePage, returns JSON response.
    case 'move_page': {
      const { pageId, targetSpaceKey, parentId } = args as {
        pageId: string;
        targetSpaceKey: string;
        parentId?: string;
      };
      
      const page = await confluenceClient.movePage(pageId, targetSpaceKey, parentId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(page, null, 2)
          }
        ]
      };
    }
  • TypeScript interface defining the MovePageRequest structure used in the movePage implementation.
    export interface MovePageRequest {
      version: {
        number: number;
      };
      title: string;
      type: string;
      space: {
        key: string;
      };
      ancestors?: Array<{
        id: string;
      }>;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action 'move' but doesn't disclose behavioral traits such as whether this requires specific permissions, if it's reversible, what happens to child pages, or potential side effects (e.g., broken links). This leaves significant gaps 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 that directly states the tool's purpose with no wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, effects), usage context, and return values, leaving the agent with insufficient information for safe and effective invocation.

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 fully documents all three parameters (pageId, parentId, targetSpaceKey). The description adds no additional meaning beyond implying the parameters relate to moving, which is already clear from the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'move' and the resource 'Confluence page', specifying the action of relocating to a different space or parent. It distinguishes from siblings like 'update_page' (which modifies content) and 'get_page' (which retrieves), but doesn't explicitly differentiate from all siblings (e.g., 'create_page' is distinct).

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. It doesn't mention prerequisites (e.g., needing page IDs), exclusions (e.g., not for moving multiple pages), or comparisons to other tools like 'update_page' for other modifications.

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