Create a new folder in a Confluence space by providing space ID and title, with optional parent ID to place it under a specific page or folder.
Create a folder in a Confluence space, optionally under a parent page or folder.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| space_id | Yes | ||
| max_chars | No | ||
| parent_id | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only mentions optional placement under a parent, but does not describe side effects, error behavior, permissions, or whether the folder is created idempotently. Agents cannot anticipate consequences of calling this tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler. Every word earns its place, and the core action and optional placement are stated efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a create operation with 4 parameters, no output schema, and no annotations, the description is too thin. It does not explain 'max_chars', required space context, or outcomes, leaving an agent without enough information to invoke the tool correctly and safely.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It clarifies that 'parent_id' refers to a parent page or folder, but leaves 'max_chars' and the exact semantics of 'space_id' and 'title' unexplained. The description adds minimal meaning beyond the raw parameter names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('create') on a specific resource ('folder') within a Confluence space, and mentions the optional parent placement. The resource 'folder' clearly distinguishes it from sibling tools like 'confluence_create_page'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives such as creating a page or using raw_request. There are no prerequisites, exclusions, or decision criteria provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.