Skip to main content
Glama
Sign In
atlassian-browser-mcp

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Page

confluence_create_page

Creates a new Confluence page in a specified space from Markdown, wiki, or storage-format content, optionally under a parent page.

Instructions

Create a new Confluence page.

Input Schema

NameRequiredDescriptionDefault
emojiNo(Optional) Page title emoji (icon shown in navigation). Can be any emoji character like '📝', '🚀', '📚'. Set to null/None to remove.
titleYesThe title of the page
contentNoThe content of the page. Format depends on content_format parameter. Can be Markdown (default), wiki markup, storage format, or XHTML storage format. Either 'content' or 'content_file' must be provided, but not both.
subtypeNo(Optional) Confluence page subtype. Use 'live' to create a Confluence Live Doc. Only supported for Confluence Cloud.
parent_idNo(Optional) parent page ID. If provided, this page will be created as a child of the specified page
space_keyYesThe key of the space to create the page in (usually a short uppercase code like 'DEV', 'TEAM', or 'DOC')
page_widthNo(Optional) Page layout width. Options: 'full-width', 'default'. Defaults to null (Confluence default).
content_fileNo(Optional) Absolute or relative filesystem path to read the page body from (UTF-8). Use this instead of 'content' when the body is too large to pass comfortably as a tool argument. Mutually exclusive with 'content'.
table_layoutNo(Optional) Table width preset applied to all markdown tables. Options: 'full-width' (1800 px), 'wide' (960 px), 'default' (760 px). Only applies when content_format is 'markdown'.
content_formatNo(Optional) The format of the content parameter. Options: 'markdown' (default), 'wiki', 'storage', or 'xhtml'. Use 'xhtml' when providing Confluence XHTML storage format (same as 'storage'). Wiki format uses Confluence wiki markup syntaxmarkdown
include_contentNo(Optional) Whether to include page content in the response. Defaults to false since callers already have the content at create time
enable_heading_anchorsNo(Optional) Whether to enable automatic heading anchor generation. Only applies when content_format is 'markdown'

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / subtype
      Added value: +{
+  "default": null,
+  "description": "(Optional) Confluence page subtype. Use 'live' to create a Confluence Live Doc. Only supported for Confluence Cloud.",
+  "type": "string"
+}
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Changed7 schema fields changedv1.2.1
    • addedInput schema / properties / content / default
      Added value: +null
    • changedInput schema / properties / content / description
      Previous value: -"The content of the page. Format depends on content_format parameter. Can be Markdown (default), wiki markup, or storage format"New value: +"The content of the page. Format depends on content_format parameter. Can be Markdown (default), wiki markup, storage format, or XHTML storage format. Either 'content' or 'content_file' must be provided, but not both."
    • addedInput schema / properties / content_file
      Added value: +{
+  "default": null,
+  "description": "(Optional) Absolute or relative filesystem path to read the page body from (UTF-8). Use this instead of 'content' when the body is too large to pass comfortably as a tool argument. Mutually exclusive with 'content'.",
+  "type": "string"
+}
    • changedInput schema / properties / content_format / description
      Previous value: -"(Optional) The format of the content parameter. Options: 'markdown' (default), 'wiki', or 'storage'. Wiki format uses Confluence wiki markup syntax"New value: +"(Optional) The format of the content parameter. Options: 'markdown' (default), 'wiki', 'storage', or 'xhtml'. Use 'xhtml' when providing Confluence XHTML storage format (same as 'storage'). Wiki format uses Confluence wiki markup syntax"
    • addedInput schema / properties / page_width
      Added value: +{
+  "default": null,
+  "description": "(Optional) Page layout width. Options: 'full-width', 'default'. Defaults to null (Confluence default).",
+  "type": "string"
+}
    • addedInput schema / properties / table_layout
      Added value: +{
+  "default": null,
+  "description": "(Optional) Table width preset applied to all markdown tables. Options: 'full-width' (1800 px), 'wide' (960 px), 'default' (760 px). Only applies when content_format is 'markdown'.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "space_key",
-  "title",
-  "content"
-]New value: +[
+  "space_key",
+  "title"
+]
  3. Addedv1.0.1

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is covered. The description adds nothing beyond that: no mention that content and content_file are mutually exclusive, that creation requires space write permission, or that repeat calls create duplicates (non-idempotent). For a 12-parameter write tool, that is a thin contribution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is front-loaded and wastes no words, but it is undersized for a 12-parameter mutation tool — it is under-specified rather than tight. There is room to add routing information without bloat.

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?

The schema and annotations are rich and an output schema exists, so return values need no explanation. Still, the description omits the decision-relevant context: how this differs from create_page_from_template and copy_page, and any caveats around content sourcing. For a page-creation tool in a crowded sibling set, that leaves a real gap.

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 every parameter including content/content_file exclusivity, subtype, page_width and content_format is already documented in the schema. The description adds no parameter meaning beyond what the schema provides, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a clear verb+resource ("Create a new Confluence page"), so an agent knows what it does at a glance. However, it offers no differentiation from close siblings such as confluence_create_page_from_template or confluence_copy_page, which also produce pages. Purpose is stated but not disambiguated.

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?

There is no guidance on when to use this tool versus the alternative page-creation paths (from template, copy). No prerequisites are mentioned either, such as needing a valid space_key the user can write to. Usage must be inferred entirely from the name.

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

Deploy Server

Other Tools