Skip to main content
Glama

list_issues

Retrieve project issues by status, priority, label, module, and date range. Filter for workable or blocked issues to manage dependencies.

Instructions

List issues for a project. workable=true gives issues with no blockers, blocked=true for issues with at least one blocker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoFilter by label name
limitNoMax results (default 50)
orderNoSort direction: asc (default) or desc
moduleNoFilter by module name
offsetNoZero-indexed offset for paging
statusNoFilter by status: backlog, todo, active, done, cancelled
blockedNoReturn issues with at least one blocker.
projectYesProject ID (e.g. LIF)
order_byNoSort Order: sort_order (default), sequence, created, updated, priority
priorityNoFilter by priority: urgent, high, medium, low, none
workableNoOnly return issues with no unresolved blockers
created_sinceNoCreated at/after ISO date or datetime (e.g. 2026-06-01)
created_untilNoCreated before ISO date or datetime (exclusive)
updated_sinceNoUpdated at/after ISO date or datetime.
updated_untilNoUpdated before ISO date or datetime (exclusive)
Behavior2/5

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

With no annotations, the description should disclose key behaviors like pagination defaults, sorting, and return format. It only explains two boolean parameters (workable, blocked), missing critical information about rate limits, response structure, or side effects.

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 extremely concise with one sentence followed by parameter clarifications. No extraneous content; every word serves a purpose.

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

Completeness2/5

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

Given 15 parameters and no output schema, the description is incomplete. It fails to specify default limit (50), default sorting, pagination behavior, or response structure. An agent lacks sufficient information to confidently use this tool without exploring.

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 coverage is 100%, so each parameter has a schema description. The tool description adds value by clarifying 'workable' and 'blocked' in plain language, but does not explain other parameters like created_since or format expectations. Baseline 3 is appropriate.

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's function: 'List issues for a project.' The verb 'list' and resource 'issues' are specific. It distinguishes from siblings like get_issue (single issue) and create_issue (creation). However, it does not explicitly state that it returns all issues by default, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives such as get_issue or list_comments. The description does not mention the default behavior, pagination, or common use cases, leaving the agent without context for selection.

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/VoidNullable/lific'

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