Skip to main content
Glama

Confluence

by io.github.pipeworx-io

Confluence Create Page

confluence_create_page
Idempotent

Create a new Confluence page with title and content. Specify parent page ID or space key (e.g., "ENG"). Returns page ID and URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesPage body content in Confluence storage format (XHTML)
titleYesPage title
statusNoPage status: "current" (published) or "draft". Default: "current"
spaceIdYesSpace ID to create the page in
parentIdNoParent page ID (optional, for nesting)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Created page details with ID and metadata",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "body": "<p>This is the API documentation page.</p>",
+    "spaceId": "ENG",
+    "title": "API Documentation"
+  },
+  {
+    "body": "<h1>Q4 Goals</h1><p>Revenue targets and initiatives.</p>",
+    "parentId": "11111",
+    "spaceId": "SALES",
+    "status": "draft",
+    "title": "Q4 Planning"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's mention of 'Create' aligns but adds no new behavioral insights. The idempotentHint=true is noted but not elaborated. The description adds value by mentioning the return format but does not address potential side effects or error conditions.

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 two sentences long, front-loads the core action, and contains no extraneous information. Every word serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is brief but sufficient for a creation tool, especially given that an output schema exists (as per context signals). It covers the essential input (title, content, location) and output (page ID, URL). Minor gaps like error handling or idempotency are not critical for this tool type.

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 coverage is 100%, so baseline is 3. The description mentions 'title and content' and 'parent page ID or space key', which slightly augments the schema's parameter descriptions but does not add significant new meaning beyond what the schema provides.

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 explicitly states 'Create a new Confluence page with title and content', using a specific verb and resource. It also mentions return values ('Returns page ID and URL') and distinguishes from sibling tools like confluence_get_page and confluence_list_pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by saying 'Specify parent page ID or space key (e.g., "ENG")', which guides the user on required identifiers. However, it does not explicitly state when not to use this tool versus alternatives like searching or listing pages.

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

All Confluence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

The set is dominated by near-overlapping research tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all answer factual questions with heavily overlapping descriptions, and the six polymarket_* tools plus bet_research form a second confused cluster. The five confluence_* tools are distinct, but an agent would struggle to pick among the research/betting alternatives without reading thousands of words of caveats.

Naming Consistency2/5

Most names are snake_case, but the conventions are mixed: verb_noun (confluence_create_page, validate_claim), noun_verb (bet_research), prefixed nouns (polymarket_arbitrage, pipeworx_feedback), and bare verbs (recall, forget). The glaring issue is that the server is named Confluence yet only 5 of 36 tools carry the confluence_ prefix, leaving the other 31 tools with no thematic prefix and no consistent pattern.

Tool Count2/5

36 tools is already in the 'too many' range, but the mismatch is deeper: only 5 tools relate to Confluence while 31 tools cover an entirely different domain (Pipeworx data research, prediction markets, subscriptions). For a wiki server this is wildly over-scoped; as a combined surface it is bloated and lacks a unifying purpose.

Completeness2/5

For the Confluence domain the surface is incomplete: pages can be created, fetched, listed, and searched, but there is no update_page, delete_page, comment, attachment, or content-type coverage, leaving obvious CRUD dead ends. For the Pipeworx domain, coverage is broad but disorganized, with overlapping research paths and no clear hierarchy.

Resources