MCP Atlassian Server

confluence_create_page

Create a new Confluence page by specifying the target space, page title, and content. Optionally set a parent page to organize the page hierarchically.

Instructions

Create a new page in Confluence

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "spaceKey": "<spaceKey>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "confluence_create_page"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	The title of the new page
`content`	Yes	The content of the page in Confluence storage format
`parentId`	No	Optional ID of the parent page
`spaceKey`	Yes	The key of the space to create the page in

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Without annotations, the description carries full responsibility for behavioral disclosure. It fails to mention important traits such as required permissions, side effects (e.g., auto-saving, notifications), any constraints on content (e.g., required Confluence storage format), or whether the operation is idempotent. This is a significant gap for a creation 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, direct sentence ('Create a new page in Confluence') with no fluff. Every word earned its place, and it is immediately understandable without parsing.

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 no output schema and no annotations, the description should provide more context about return behavior, error handling, or critical input details (e.g., that content must be in Confluence storage format). It is too sparse to reliably guide an agent through a successful 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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters. It does not explain how parameters interact (e.g., parentId usage) or emphasize required fields, but the schema itself is sufficient for basic 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 'Create a new page in Confluence' clearly states the action and resource. It distinguishes from sibling tools like confluence_update_page (update) and confluence_get_page (get) through the verb 'create'. However, it provides no additional context about scope or special behaviors, but remains unambiguous.

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 offers no guidance on when to use this tool versus alternatives such as confluence_update_page or Jira tools. There is no mention of prerequisites, typical scenarios, or exclusions, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server