JIRA MCP Server

confluence_create_page

Create a Confluence page in a specified space by providing title, content, and optional parent page ID.

Instructions

Crea una nuova pagina Confluence in uno spazio specificato.

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	Titolo della pagina
`content`	Yes	Contenuto in formato storage XHTML di Confluence (oppure testo semplice)
`parentId`	No	ID della pagina padre (opzionale)
`spaceKey`	Yes	Chiave dello spazio (es. DEV)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 8, 2026

TDQS

B3.1/5.0

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 fails to mention any behavioral traits such as whether duplicate titles are allowed, authentication requirements, potential errors, or the format of the response.

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

Conciseness4/5

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

The description is a single, short sentence that efficiently conveys the core purpose. It is front-loaded and concise, though it sacrifices completeness for brevity.

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 tool has 4 parameters, no output schema, and no annotations, the description is too minimal. It omits critical context such as what the tool returns, how to handle errors, or how to specify the parent page hierarchy.

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 the schema; it only repeats that the tool creates a page without elaborating on parameter relationships or usage hints.

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

Purpose5/5

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

The description 'Crea una nuova pagina Confluence in uno spazio specificato' clearly states the action (create) and resource (new Confluence page in a specified space). It directly distinguishes from sibling tools like 'confluence_update_page' and 'confluence_get_page' by using the verb 'crea' (create).

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. There is no mention of typical scenarios, prerequisites, or explicit comparison to sibling tools like 'confluence_update_page' for updating existing pages.

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