Skip to main content
Glama

List Issues

list_issues
Read-onlyIdempotent

Retrieve a paginated list of MantisBT issues with filters by project, status, assignee, reporter, and dates. Use select parameter to limit fields and reduce response size.

Instructions

List MantisBT issues with optional filtering. Returns a paginated list of issues. Use the "select" parameter to limit returned fields and reduce response size significantly.

Note: "assigned_to", "reporter_id", "status", and date filters are applied client-side (the MantisBT REST API does not support these as server-side filters). When any of these filters are active the tool automatically fetches multiple pages internally until enough matching results are found (up to 500 issues scanned). The "page" and "page_size" parameters refer to the resulting filtered list.

Tip for date queries: fetching with select="id,updated_at,created_at" plus a date filter is very compact and efficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoFilter by project ID
pageNoPage number (default: 1)
page_sizeNoIssues per page (default: 50, max: 50)
assigned_toNoFilter by handler/assignee user ID
reporter_idNoFilter by reporter user ID
filter_idNoUse a saved MantisBT filter ID
sortNoSort field (e.g. "last_updated", "id")
directionNoSort direction
selectNoComma-separated list of fields to include in the response (server-side projection). Significantly reduces response size. Example: "id,summary,status,priority,handler,updated_at"
statusNoFilter issues by status name (e.g. "new", "feedback", "acknowledged", "confirmed", "assigned", "resolved", "closed") or use "open" as shorthand for all statuses with id < 80 (i.e. not yet resolved or closed). Applied client-side after fetching — when combined with pagination, a page may contain fewer results than page_size.
updated_afterNoISO-8601 timestamp — only return issues updated after this date (exclusive). Example: "2026-03-25T00:00:00Z"
updated_beforeNoISO-8601 timestamp — only return issues updated before this date (exclusive). Example: "2026-03-28T00:00:00Z"
created_afterNoISO-8601 timestamp — only return issues created after this date (exclusive). Example: "2026-03-01T00:00:00Z"
created_beforeNoISO-8601 timestamp — only return issues created before this date (exclusive). Example: "2026-03-15T00:00:00Z"
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. The description adds significant behavioral context: client-side filter application, automatic internal pagination up to 500 issues, and how page/page_size refer to filtered results. No contradiction with annotations.

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

Conciseness4/5

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

Description is well-structured with a front-loaded main sentence, a note, and a tip. It efficiently conveys important information, though slightly verbose with the note about page/page_size (already explained earlier).

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 14 parameters, no output schema, and non-standard client-side filtering, the description covers the essential behavioral nuances and provides practical advice. Lacks a brief mention of the typical response structure beyond 'paginated list of issues', but this is a minor gap.

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 has 100% coverage, baseline 3. The description adds meaning beyond schema by explaining client-side filter behavior for specific parameters (assigned_to, reporter_id, status, dates), and the interplay with pagination. Also provides a practical tip for date queries using select.

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 MantisBT issues with optional filtering', specifying verb and resource. However, it does not distinguish from the sibling tool 'get_issues', which may cause confusion.

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?

Provides context on client-side filtering and internal pagination, and gives a tip for efficient date queries. But lacks explicit guidance on when to use this tool vs alternatives (e.g., get_issue, get_issues).

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/dpesch/mantisbt-mcp-server'

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