Skip to main content
Glama

Create Issue

create_issue

Create a new MantisBT issue by providing summary, description, project ID, and category. Returns the full issue object with ID, status, and view URL.

Instructions

Create a new MantisBT issue. Returns the full created issue object including the assigned id, summary, status, priority, severity, category, reporter, created_at, and view_url.

Required fields: summary, description, project_id, category. All other fields are optional with sensible defaults (priority: "normal", severity: "minor").

Recommended workflow:

  1. Call get_project_categories to obtain a valid category name

  2. Optionally call get_project_versions to obtain version names

  3. Optionally call find_project_member to resolve the assignee's username

Both priority and severity accept canonical English names or localized labels from the connected MantisBT instance — call get_issue_enums to see all available values.

For the handler, prefer the username field (resolved server-side) over handler_id when working interactively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handlerNoMantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use find_project_member or get_project_users to look up valid login names.
summaryYesIssue summary/title (required)
versionNoAffected product version name. Use get_project_versions to list available version names for the project.
categoryYesCategory name (required). Use get_project_categories to list available categories for the project.
priorityNoPriority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: "normal". Use get_issue_enums to see localized labels.normal
severityNoSeverity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: "minor". Use get_issue_enums to see localized labels.minor
handler_idNoNumeric user ID of the assignee. Alternative to the handler field — use one or the other, not both.
project_idYesProject ID the issue belongs to — use list_projects to discover project IDs
view_stateNoVisibility of the issue: "public" (visible to all, default) or "private" (restricted to higher-access users).
descriptionYesDetailed issue description (required). Do not create issues without a description. Plain text or Markdown.
target_versionNoTarget fix version — version in which the issue is planned to be resolved. Use get_project_versions to list available version names.
reproducibilityNoHow reliably the issue reproduces. Canonical English names: always, sometimes, random, have not tried, unable to reproduce, N/A. Use get_issue_enums to see localized labels.
fixed_in_versionNoVersion in which the issue was fixed. Use get_project_versions to list available version names.
steps_to_reproduceNoStep-by-step instructions to reproduce the issue. Plain text or Markdown.
additional_informationNoAdditional context or notes about the issue. Plain text or Markdown.
Behavior4/5

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds that it creates the issue and returns the full object with id and other fields, but does not mention side effects beyond creation, which is sufficient given the annotations.

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, starting with purpose and return value, then required fields, followed by workflow. It uses bullet-like formatting without being verbose, earning its place with every sentence.

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?

With 15 parameters and no output schema, the description covers return value structure, required fields, defaults, and references other tools for lookups, providing a comprehensive understanding for creation.

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 each parameter has a description. The description adds global context like required fields, defaults, and localized label handling, which enhances understanding beyond individual parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new MantisBT issue' with a specific verb and resource, and the sibling tools include distinct operations like update_issue and delete_issue, so differentiation is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a 'Recommended workflow' section with explicit steps (calling get_project_categories, get_project_versions, find_project_member) and guidance on using handler vs handler_id, providing clear when-to-use instructions.

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