Skip to main content
Glama
vish288

mcp-atlassian-extended

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Jira Backlog

jira_backlog
Read-onlyIdempotent

Fetch backlog issues for a Jira board with a compact set of fields by default, or specify fields to return extra issue details.

Instructions

Get backlog issues for a board.

Returns a compact field set by default (summary, status, issue type, priority, assignee, labels). Pass fields (e.g. *all) to widen it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated Jira fields to return. Defaults to a compact set; pass '*all' for every field (large responses).summary,status,issuetype,priority,assignee,labels
board_idYesBoard ID
start_atNoIndex of the first result (use next_start_at to page)
max_resultsNoMaximum results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.1
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "summary,status,issuetype,priority,assignee,labels",
+  "description": "Comma-separated Jira fields to return. Defaults to a compact set; pass '*all' for every field (large responses).",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed1 schema field changedv0.8.1
    • addedInput schema / properties / start_at
      Added value: +{
+  "default": 0,
+  "description": "Index of the first result (use next_start_at to page)",
+  "minimum": 0,
+  "type": "integer"
+}
  3. First observedv0.6.13

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered without the description. The description's one added behavioral fact — that a compact field set is returned by default and ``*all`` widens it — largely restates the schema text for ``fields``, so it contributes little beyond structured data.

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 short sentences, front-loaded with the core purpose followed immediately by the return-shape note. Nothing is padded and no sentence is redundant.

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 read-only list tool with full schema coverage and clear annotations, the description plus schema cover what an agent needs to invoke it; pagination is documented via start_at/max_results/next_start_at in the schema. Minor gap: no hint about ordering or total counts, but those are secondary here.

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 compact-default and '*all' semantics are already documented in the ``fields`` property, including the large-response warning. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get backlog issues for a board" states a specific verb (Get) plus resource (backlog issues) and scope (per board), which is enough for an agent to distinguish it from jira_get_sprint or jira_get_board. It stops short of explicitly naming a sibling or the boundary conditions that separate backlog from sprint queries.

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?

The description gives no when-to-use guidance and never mentions alternatives such as jira_get_sprint or issue search tools, even though the sibling list contains several plausible confusables. The only usage hint is about the ``fields`` parameter, not about when to select this tool.

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