Skip to main content
Glama

confluence_set_page_property

Set or update a content property on a Confluence page. Define a key and JSON value to store metadata like status or priority.

Instructions

Set a content property on a Confluence page.

Creates the property if it doesn't exist, or updates it if it does.
The value is stored as a JSON string.

Args:
    page_id: A numeric page ID or a Confluence URL (including short /wiki/x/ links).
    key: The property key (e.g. "status", "priority").
    value: The property value as a JSON string (e.g. '"done"', '{"score": 5}').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
valueYes
page_idYes
Behavior4/5

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

Despite no annotations, the description transparently explains the create-or-update behavior and that the value is stored as a JSON string, which is critical for correct usage.

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 concise, well-structured with a clear purpose sentence followed by behavioral notes and parameter definitions. Every sentence adds value.

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?

Given no output schema and no annotations, the description covers the essential aspects: what the tool does, parameter details, and value format. Missing return value info but still adequate for a set operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description fully compensates by detailing each parameter: page_id accepts numeric ID or Confluence URL, key is a property key, value must be a JSON string.

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 clearly states it sets a content property on a Confluence page, with an upsert behavior. It distinguishes from sibling tools that focus on page editing, labels, or other actions.

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?

No guidance on when to use this tool versus alternatives. The user must infer from sibling tool names, but no explicit when-not or alternative tool references.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karbassi/confluence-adf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server