Skip to main content
Glama
Sign In
Backlog MCP Server

Backlog MCP Server

by nulab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_issues

Read-only

Retrieve a filtered, sorted, paginated list of Backlog issues by project, status, assignee, priority, dates, or custom fields to support project tracking.

Instructions

Returns list of issues

Input Schema

NameRequiredDescriptionDefault
sortNoSort field
countNoNumber of issues to retrieve
orderNoSort order
offsetNoOffset for pagination
keywordNoKeyword to search for in issues
statusIdNoStatus IDs
projectIdNoProject IDs
versionIdNoVersion IDs
assigneeIdNoAssignee user IDs
categoryIdNoCategory IDs
priorityIdNoPriority IDs
issueTypeIdNoIssue type IDs
milestoneIdNoMilestone IDs
createdSinceNoCreated since (yyyy-MM-dd)
createdUntilNoCreated until (yyyy-MM-dd)
customFieldsNoCustom field filters (text, numeric, date, or list)
dueDateSinceNoDue date since (yyyy-MM-dd)
dueDateUntilNoDue date until (yyyy-MM-dd)
resolutionIdNoResolution IDs
updatedSinceNoUpdated since (yyyy-MM-dd)
updatedUntilNoUpdated until (yyyy-MM-dd)
createdUserIdNoCreated user IDs
parentIssueIdNoParent issue IDs
startDateSinceNoStart date since (yyyy-MM-dd)
startDateUntilNoStart date until (yyyy-MM-dd)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.1
  2. Removedv0.13.1
  3. Changed1 schema field changedv0.11.0
    • addedInput schema / properties / organization
      Added value: +{
+  "description": "Optional organization name. Use list_organizations to inspect available organizations.",
+  "type": "string"
+}
  4. Changed1 schema field changedv1.0.0
    • addedInput schema / properties / customFields
      Added value: +{
+  "description": "Custom field filters (text, numeric, date, or list)",
+  "items": {
+    "anyOf": [
+      {
+        "additionalProperties": false,
+        "description": "Text custom field filter",
+        "properties": {
+          "id": {
+            "description": "Custom field ID (e.g., 12345)",
+            "type": "number"
+          },
+          "type": {
+            "const": "text",
+            "type": "string"
+          },
+          "value": {
+            "description": "Keyword to match for the custom field",
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "id",
+          "value"
+        ],
+        "type": "object"
+      },
+      {
+        "additionalProperties": false,
+        "description": "Numeric custom field filter",
+        "properties": {
+          "id": {
+            "description": "Custom field ID (e.g., 12345)",
+            "type": "number"
+          },
+          "max": {
+            "description": "Maximum numeric value (inclusive)",
+            "type": "number"
+          },
+          "min": {
+            "description": "Minimum numeric value (inclusive)",
+            "type": "number"
+          },
+          "type": {
+            "const": "numeric",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "id"
+        ],
+        "type": "object"
+      },
+      {
+        "additionalProperties": false,
+        "description": "Date custom field filter",
+        "properties": {
+          "id": {
+            "description": "Custom field ID (e.g., 12345)",
+            "type": "number"
+          },
+          "max": {
+            "description": "End date (yyyy-MM-dd)",
+            "type": "string"
+          },
+          "min": {
+            "description": "Start date (yyyy-MM-dd)",
+            "type": "string"
+          },
+          "type": {
+            "const": "date",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "id"
+        ],
+        "type": "object"
+      },
+      {
+        "additionalProperties": false,
+        "description": "List custom field filter",
+        "properties": {
+          "id": {
+            "description": "Custom field ID (e.g., 12345)",
+            "type": "number"
+          },
+          "type": {
+            "const": "list",
+            "type": "string"
+          },
+          "value": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "items": {
+                  "type": "number"
+                },
+                "minItems": 1,
+                "type": "array"
+              }
+            ],
+            "description": "Value ID(s) to match for list-type custom field"
+          }
+        },
+        "required": [
+          "type",
+          "id",
+          "value"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  "type": "array"
+}
  5. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered elsewhere. The description adds nothing beyond that: no note on default page size, ordering defaults when sort/order are omitted, whether filters combine with AND, or how large result sets behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four words with no padding and nothing buried, so structurally clean and front-loaded. But the brevity comes from omission rather than economy - there is no substantive content to be concise about.

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

Completeness1/5

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

A 25-parameter, zero-required retrieval tool with pagination, sorting, date ranges, and polymorphic custom-field filters gets a five-word description and no output schema. Nothing tells the agent how to page, what the defaults are, or what shape the returned list takes - completely inadequate for the complexity.

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 all 25 parameters including the nested customFields oneOf variants are documented in the schema itself; baseline 3 applies. The description contributes zero additional meaning - notably it never explains whether the many ID-array filters are ORed within a field and ANDed across fields, which is the main ambiguity the schema leaves.

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

Purpose2/5

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

"Returns list of issues" restates the tool name almost verbatim; the only added signal is the plural "list", which weakly implies bulk retrieval versus the sibling get_issue. It names no scope, no filter semantics, and does not distinguish itself from count_issues, get_issue, or get_related_issues.

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?

There is no when-to-use guidance at all: no mention that this is the filtered/bulk retrieval path, no pointer to count_issues for totals, no note that get_issue should be used for a single issue by ID. The agent must infer routing from sibling names alone.

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