Skip to main content
Glama
dpesch

MantisBT MCP Server

by dpesch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Issues

list_issues
Read-onlyIdempotent

Retrieve MantisBT issues with optional filters for project, status, assignee, reporter, and dates. Supports pagination, sorting, and field selection to control 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
pageNoPage number (default: 1)
sortNoSort field (e.g. "last_updated", "id")
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.
directionNoSort direction
filter_idNoUse a saved MantisBT filter ID
page_sizeNoIssues per page (default: 50, max: 50)
project_idNoFilter by project ID
assigned_toNoFilter by handler/assignee user ID
reporter_idNoFilter by reporter user ID
created_afterNoISO-8601 timestamp — only return issues created after this date (exclusive). Example: "2026-03-01T00:00:00Z"
updated_afterNoISO-8601 timestamp — only return issues updated after this date (exclusive). Example: "2026-03-25T00:00:00Z"
created_beforeNoISO-8601 timestamp — only return issues created before this date (exclusive). Example: "2026-03-15T00:00:00Z"
updated_beforeNoISO-8601 timestamp — only return issues updated before this date (exclusive). Example: "2026-03-28T00:00:00Z"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / assigned_to / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / filter_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / project_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / reporter_id / maximum
      Added value: +9007199254740991
  2. Addedv1.10.4
  3. Removed
  4. Changed4 schema fields changedv1.5.15
    • addedInput schema / properties / created_after
      Added value: +{
+  "description": "ISO-8601 timestamp — only return issues created after this date (exclusive). Example: \"2026-03-01T00:00:00Z\"",
+  "type": "string"
+}
    • addedInput schema / properties / created_before
      Added value: +{
+  "description": "ISO-8601 timestamp — only return issues created before this date (exclusive). Example: \"2026-03-15T00:00:00Z\"",
+  "type": "string"
+}
    • addedInput schema / properties / updated_after
      Added value: +{
+  "description": "ISO-8601 timestamp — only return issues updated after this date (exclusive). Example: \"2026-03-25T00:00:00Z\"",
+  "type": "string"
+}
    • addedInput schema / properties / updated_before
      Added value: +{
+  "description": "ISO-8601 timestamp — only return issues updated before this date (exclusive). Example: \"2026-03-28T00:00:00Z\"",
+  "type": "string"
+}
  5. First observedv1.5.6

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), but the description adds genuinely important behavior: four filters are applied client-side, the tool silently auto-fetches up to 500 issues across pages, and client-side filtering can make a page yield fewer than page_size results. That is context the annotations cannot convey.

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?

Front-loaded with purpose and return shape, then the caveat paragraph, then a tip. Each block earns its place, though the note paragraph and tip could be tightened slightly.

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

Completeness5/5

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

For a 14-param read/list tool with no output schema, the description covers return shape, pagination semantics, the non-obvious client-side filtering behavior, and an efficiency tip. An agent has what it needs to call this correctly; only the sibling overlap remains unaddressed.

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%, so baseline is 3, but the description adds meaning beyond the schema: it explains why "select" matters (significant response-size reduction), notes that page/page_size refer to the post-filter list, and pairs select with date filters for efficiency. It does not, however, resolve semantics for sort, filter_id, or client-vs-server filter interactions in detail.

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?

States a specific verb and resource ("List MantisBT issues") with scope ("with optional filtering") and return shape ("paginated list"). However, it does not differentiate itself from the sibling get_issues, which appears to be an overlapping listing tool, leaving ambiguity an agent must resolve by opening schemas.

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?

It gives useful in-tool guidance (use "select" to shrink responses, a date-query tip), but never states when to choose this over get_issue or get_issues, nor any prerequisites. Usage is implied rather than contrasted with alternatives.

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