Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

confluence_move

Reposition a Confluence page inside the same space: set a target as new parent, or place it before/after as a sibling. Returns updated page metadata.

Instructions

Move or reparent a Confluence page within its current space. position is "append" (default — target becomes new parent), "before", or "after" (sibling reorder relative to target). Same-space only — cross-space moves are not supported. Returns the moved page's metadata as YAML (id, title, parent_id, ancestors). Mirrors omni-dev atlassian confluence move.

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": {
      "page_id": "<page_id>",
      "target_id": "<target_id>"
    },
    "name": "confluence_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesID of the Confluence page to move.
positionNoPosition relative to the target. Defaults to `"append"`. Accepted values: `"append"` (target becomes new parent), `"before"`, `"after"`. Same-space only — cross-space moves are not supported.
target_idYesTarget page ID — new parent for `position: "append"`, or sibling reference for `"before"`/`"after"`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `confluence_move` tool."
    • removedInput schema / title
      Removed value: -"ConfluenceMoveParams"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the returned YAML metadata (id, title, parent_id, ancestors), the three position behaviors, and the same-space limitation. Does not mention permission requirements or side effects on page content/attachments, but covers key behavioral aspects.

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?

Three sentences, no wasted words. Front-loaded with action, followed by position semantics, constraint, and return format. Every sentence earns its place.

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

Completeness5/5

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

Given no output schema, description adequately specifies return format. Parameters are fully described with added context. Constraints are clear. The tool is well-situated among sibling tools with a distinct identity.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value by clarifying position defaults ('append'), explaining each position meaning in context, and elaborating target_id's role relative to position. This exceeds schema descriptions.

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?

Clearly states 'Move or reparent a Confluence page within its current space.' Uses specific verb and resource. Distinguishes from sibling tools like confluence_create, confluence_delete, etc., by focusing solely on moving/reparenting.

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?

Provides explicit constraint 'Same-space only — cross-space moves are not supported,' helping the agent avoid misuse. Explains position options. Lacks explicit comparison to alternative tools for cross-space scenarios, but the constraint effectively guides when not to use.

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