Skip to main content
Glama

backlog_list

List tasks from a backlog with filters by status, type, epic, parent, or text query. Returns recently updated items first, default shows active tasks.

Instructions

List tasks from backlog. Returns most recently updated items first. Default: shows only active work (open/in_progress/blocked), limited to 20 items. Use counts=true to check if more items exist beyond the limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by status. Options: open, in_progress, blocked, done, cancelled. Default: [open, in_progress, blocked]. Pass ["done"] to see completed work.
typeNoFilter by type. Options: task, epic, folder, artifact, milestone. Default: returns all.
epic_idNoFilter tasks belonging to a specific epic. Example: epic_id="EPIC-0001"
parent_idNoFilter items by parent. Example: parent_id="FLDR-0001"
queryNoSearch across all task fields (title, content, evidence, references, etc.). Case-insensitive substring matching.
countsNoInclude global counts { total_tasks, total_epics, by_status, by_type } alongside results. Use this to detect if more items exist beyond the limit. Default: false
limitNoMax items to return. Default: 20. Increase if you need to see more items (e.g., limit=100 to list all epics).
Behavior4/5

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

With no annotations, the description carries full burden. It discloses default filters (open/in_progress/blocked), limit (20), ordering (most recent first), and counts parameter behavior. No side effects or auth needs mentioned, but sufficient for a read-only list tool.

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. Every sentence adds critical information: what the tool does, ordering, defaults, and a tip for pagination. Extremely efficient.

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?

Given 7 parameters all documented in schema and no output schema, the description covers essential defaults and ordering. It could mention that the tool can list epics or other types via the type parameter, but the schema covers that. Mostly complete.

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% with parameter descriptions. The tool description adds value beyond schema by stating default statuses, default limit, and ordering. It also explains the counts parameter's purpose, which is not in the schema description.

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 'List tasks from backlog' with details on ordering and defaults. It implicitly distinguishes from backlog_get and backlog_search by focusing on listing with filters, but does not explicitly differentiate from siblings.

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 description implies usage for listing backlog items with defaults, and hints at using counts=true for pagination detection. However, it lacks explicit guidance on when to use this tool versus alternatives like backlog_search (for text search) or backlog_get (for single items).

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/gkoreli/backlog-mcp'

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