Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

confluence_label_list

Retrieve labels from a Confluence page with automatic pagination. Set limit to 0 to return every label, or specify a maximum number.

Instructions

List labels on a Confluence page (auto-paginated). limit of 0 returns every label. Mirrors omni-dev atlassian confluence label list.

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>"
    },
    "name": "confluence_label_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesConfluence page ID.
limitNoMaximum number of labels to return (0 = unlimited).

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_list` tool."
    • removedInput schema / title
      Removed value: -"ConfluenceLabelListParams"
  4. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It mentions auto-pagination and the limit behavior but does not explicitly state that it is a read-only operation or disclose any other behavioral traits.

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 with no redundancy. The first sentence gives the core purpose and auto-pagination, the second adds a key detail and a reference command. Every word earns its place.

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

Completeness3/5

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

With no output schema, the description does not explain what the tool returns (e.g., label names, IDs) or error conditions. However, for a simple list tool with two parameters, the information is mostly adequate but leaves some gaps.

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%, describing both parameters. The description adds context beyond the schema by explaining auto-pagination and that limit=0 returns all labels, which enhances understanding.

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 'List labels on a Confluence page' with a specific verb and resource. It includes auto-pagination and the notable limit=0 behavior, and distinguishes from sibling tools like add/remove.

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 explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or provide comparisons to other listing tools, leaving the agent without decision support.

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