Jira Cloud MCP Server

get_all_labels

Retrieve all labels used in Jira Cloud to review or reuse existing tags. Supports pagination to handle large label lists.

Instructions

Get all labels

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_labels"
  }
}

Input Schema

Name	Required	Description	Default
`startAt`	No	The index of the first item to return in a page of results (page offset).
`maxResults`	No	The maximum number of items to return per page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Get all labels' implies a complete retrieval, but the pagination parameters suggest this tool returns only one page; the description does not disclose that fact or explain how to obtain all labels.

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 three words long, with no filler, and every word contributes meaning. It is a model of concise, front-loaded clarity.

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?

For a simple read tool with optional pagination parameters, the description is minimally viable for a basic call. However, it lacks context about pagination behavior and return format, which matters when the agent needs to retrieve all labels beyond the default page size.

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

Parameters3/5

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

Schema description coverage is 100%, so the parameters 'startAt' and 'maxResults' are already fully documented in the schema. The description adds no additional meaning beyond what the schema provides, matching the baseline for high schema coverage.

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 'Get all labels' uses a specific verb ('Get') and a clearly identified resource ('all labels'), and there are no sibling tools with a similar or overlapping purpose, so an agent can unambiguously tell what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The name makes the intended use implicit: call this when labels need to be retrieved. However, the description gives no explicit guidance about when to prefer this tool, whether pagination should be iterated to truly get 'all' labels, or any exclusions/alternatives.

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

Deploy Server