Skip to main content
Glama
Olson3R
by Olson3R

create_page

Generate a new Confluence page with specified space, title, content, and optional parent page ID using secure access through the Confluence MCP Server.

Instructions

Create a new Confluence page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesPage content (HTML or storage format)
parentIdNoOptional: Parent page ID
spaceKeyYesTarget space key
titleYesPage title

Implementation Reference

  • MCP tool handler for 'create_page': destructures input arguments, calls ConfluenceClient.createPage, and returns the created page as formatted JSON text.
    case 'create_page': {
      const { spaceKey, title, content, parentId } = args as {
        spaceKey: string;
        title: string;
        content: string;
        parentId?: string;
      };
      
      const page = await confluenceClient.createPage(spaceKey, title, content, parentId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(page, null, 2)
          }
        ]
      };
    }
  • src/index.ts:88-113 (registration)
    Registration of the 'create_page' tool in ListToolsRequestHandler, defining name, description, and JSON input schema.
    {
      name: 'create_page',
      description: 'Create a new Confluence page',
      inputSchema: {
        type: 'object',
        properties: {
          spaceKey: {
            type: 'string',
            description: 'Target space key'
          },
          title: {
            type: 'string',
            description: 'Page title'
          },
          content: {
            type: 'string',
            description: 'Page content (HTML or storage format)'
          },
          parentId: {
            type: 'string',
            description: 'Optional: Parent page ID'
          }
        },
        required: ['spaceKey', 'title', 'content']
      }
    },
  • TypeScript interface defining the Confluence API request body structure for creating a page.
    export interface CreatePageRequest {
      spaceId: string;
      status: string;
      title: string;
      body: {
        representation: string;
        value: string;
      };
      parentId?: string;
    }
  • ConfluenceClient.createPage implementation: validates space access, resolves space ID, builds CreatePageRequest, POSTs to /pages API endpoint, returns created page.
    async createPage(
      spaceKey: string, 
      title: string, 
      content: string, 
      parentId?: string
    ): Promise<ConfluencePage> {
      if (!validateSpaceAccess(spaceKey, this.config.allowedSpaces)) {
        throw new Error(`Access denied to space: ${spaceKey}`);
      }
    
      // Get space details to obtain the space ID
      const space = await this.getSpaceByKey(spaceKey);
      if (!space.id) {
        throw new Error(`Unable to get space ID for space: ${spaceKey}`);
      }
    
      const pageData: CreatePageRequest = {
        spaceId: space.id,
        status: 'current',
        title,
        body: {
          representation: 'storage',
          value: content
        }
      };
    
      if (parentId) {
        pageData.parentId = parentId;
      }
    
      const response: AxiosResponse<ConfluencePage> = await this.client.post('/pages', pageData);
      return response.data;
    }
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. It states 'create' which implies a write operation, but doesn't cover permissions required, rate limits, error handling, or what happens on success (e.g., returns a page ID). 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 with zero waste. It's front-loaded and directly states the tool's purpose without unnecessary elaboration, making it highly concise and well-structured.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, and usage context. For a 4-parameter tool that creates resources, more information is needed to guide effective use.

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 parameters. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or constraints. Baseline 3 is appropriate as 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 ('create') and resource ('new Confluence page'), making the purpose immediately understandable. It distinguishes from siblings like 'update_page' or 'move_page' by focusing on creation. However, it doesn't specify what distinguishes it from other creation-like operations in the sibling list, keeping it from 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. It doesn't mention prerequisites (e.g., needing a space or parent), exclusions, or comparisons to siblings like 'update_page' or 'move_page'. Usage is implied by the name but not explicitly stated.

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