Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

confluence_label_remove

Remove labels from a Confluence page. Requires explicit confirmation (confirm: true) to prevent accidental deletions.

Instructions

Remove one or more labels from a Confluence page. Destructive operation: callers must explicitly pass confirm: true for the removal to proceed; otherwise the tool refuses with an error. Mirrors omni-dev atlassian confluence label remove.

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": {
      "id": "<id>",
      "labels": "<labels>",
      "confirm": "<confirm>"
    },
    "name": "confluence_label_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesConfluence page ID.
labelsYesLabels to remove from the page.
confirmYesMust be set to `true` — destructive guard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.0
  2. Removedv0.39.0
  3. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `confluence_label_remove` tool.\n\n`confirm` must be `true` for the removal to proceed. This is the\nMCP-side guard for a destructive operation; the assistant must\nexplicitly opt in."
    • removedInput schema / title
      Removed value: -"ConfluenceLabelRemoveParams"
  4. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description bears full burden for behavioral disclosure. It marks the operation as destructive and explains the confirm guard, but does not mention other behaviors such as idempotency, error handling, or what happens if labels do not exist.

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?

Two sentences convey purpose, destruction, the critical confirm requirement, and a reference to the CLI command. No wasted words; efficiently front-loaded.

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?

For a simple 3-parameter tool with no output schema, the description covers the core purpose and the essential guardrail. It is mostly complete, though it could mention return values or behavior on missing labels.

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?

The input schema already describes all three parameters with 100% coverage. The description adds value by explicitly noting that 'confirm' must be 'true' and acts as a destructive guard, enhancing understanding beyond the schema.

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 'Remove one or more labels from a Confluence page' with a specific verb and resource. It distinguishes from sibling tools like confluence_label_add and confluence_label_list.

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 explicitly requires 'confirm: true' for the operation to proceed, serving as a usage guideline. However, it does not elaborate on when to use this tool versus alternatives like confluence_label_add.

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