Skip to main content
Glama

backlog_get_issue_list

Fetch a list of Backlog issues filtered by project, status, priority, assignee, keyword, and more. Returns a compact table with detailed summaries.

Instructions

Fetch a list of Backlog issues with optional filters.

Returns a compact table + detailed summaries for each issue.

FILTERS:

  • projectIdOrKey: project key (e.g. "MYPROJ") or numeric ID — auto-resolved. Highly recommended.

  • statusId: 1=Open, 2=InProgress, 3=Resolved, 4=Closed

  • priorityId: 2=High, 3=Normal, 4=Low

  • assigneeId: filter by specific user ID(s)

  • keyword: full-text search in summary and description

  • parentChild: 0=all, 1=child only, 2=parent only, 3=no parent, 4=no child

Array fields accept CSV string ("1,2") or JSON array ([1,2]). PAGINATION: Use offset + count to paginate. Max 100 per request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdOrKeyNoFilter by project key(s) or numeric ID(s). Comma-separated. Examples: "MYPROJ", "12345", "MYPROJ,OTHER". Auto-resolved to numeric IDs. Highly recommended.
statusIdNoFilter by status: 1=Open, 2=InProgress, 3=Resolved, 4=Closed. Accept [1,2] or "1,2"
priorityIdNoFilter by priority: 2=High, 3=Normal, 4=Low. Accept [2,3] or "2,3"
assigneeIdNoFilter by assignee user ID(s). Accept [123] or "123"
categoryIdNoFilter by category ID(s). Accept [10,11] or "10,11"
milestoneIdNoFilter by milestone ID(s). Accept [20] or "20"
keywordNoSearch keyword in summary and description
parentChildNo0=all, 1=child only, 2=parent only, 3=no parent, 4=no child
countNoNumber of issues (1–100, default 20)
offsetNoPagination offset (default 0)
sortNoSort field
orderNoSort order: asc or desc (default desc)desc
Behavior3/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It discloses pagination (offset/count, max 100), auto-resolution of project IDs, and CSV/JSON array acceptance. However, it does not mention authentication requirements, rate limits, whether the operation is read-only, or error behavior. Adequate but not comprehensive.

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 well-structured with clear headings for FILTERS and PAGINATION. It is concise, using bullet-like groupings and minimal prose. Every sentence adds value, and the space is used efficiently for the 12 parameters.

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?

Given 12 parameters and no output schema, the description covers filter semantics well but omits return value structure beyond 'compact table + detailed summaries'. For a list tool, knowing the fields of each issue would aid agent decision-making. The complexity warrants a bit more detail on output, but the filtering aspect is thorough.

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%, providing baseline 3. The description adds value by explaining enum mappings (e.g., statusId 1=Open), noting auto-resolution for projectIdOrKey, and clarifying CSV/JSON array inputs for array fields. This enriches the basic schema with practical usage details.

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?

The description clearly states the tool fetches a list of Backlog issues with optional filters, and mentions the return format (compact table + detailed summaries). However, it does not differentiate from sibling tools like backlog_get_issue (single issue) or other list tools, which would help an agent decide when to use this specific tool.

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 provides detailed filter options but does not offer explicit guidance on when to use this tool versus alternatives. There are no stated prerequisites, when-not-to-use conditions, or comparisons with sibling tools. The agent must infer usage from the tool name and filter set.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cuongph-dev-work/backlog_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server