Skip to main content
Glama

Create Issue

create_issue

Create a new MantisBT issue with a summary, description, project ID, and category; optionally set priority, severity, assignee, versions, and custom fields.

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. With response: "short" only id, summary, project, category, status, handler, created_at and view_url (default "full"; it changes to "short" in 2.0.0).

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 with include: ["categories"] to obtain a valid category name

  2. Optionally add "versions" to include to obtain version names

  3. Optionally call get_project with member_query 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_schema to see all available values.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "summary": "<summary>",
      "description": "<description>",
      "project_id": "<project_id>",
      "category": "<category>"
    },
    "name": "create_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
handlerNoMantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use get_project with member_query or include: ["users"] to look up valid login names.
summaryYesIssue summary/title (required)
versionNoAffected product version name. Use get_project with include: ["versions"] to list available version names for the project.
categoryYesCategory name (required). Use get_project with include: ["categories"] to list available categories for the project.
priorityNoPriority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: "normal". Use get_issue_schema to see localized labels.normal
responseNo"full" (default): the whole issue as MantisBT returns it, including description, notes and history. "short": only the fields that confirm the change — far fewer tokens. The default changes to "short" in 2.0.0.full
severityNoSeverity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: "minor". Use get_issue_schema 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.
custom_fieldsNoCustom field values: [{field: {id|name}, value: "<string>"}]. Use get_issue_schema or get_metadata to discover available custom fields per project.
target_versionNoTarget fix version — version in which the issue is planned to be resolved. Use get_project with include: ["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_schema to see localized labels.
fixed_in_versionNoVersion in which the issue was fixed. Use get_project with include: ["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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / response
      Added value: +{
      +  "default": "full",
      +  "description": "\"full\" (default): the whole issue as MantisBT returns it, including description, notes and history. \"short\": only the fields that confirm the change — far fewer tokens. The default changes to \"short\" in 2.0.0.",
      +  "enum": [
      +    "short",
      +    "full"
      +  ],
      +  "type": "string"
      +}
  2. Changed9 schema fields changedv1.15.0
    • changedInput schema / properties / category / description
      Previous value: -"Category name (required). Use get_project_categories to list available categories for the project."New value: +"Category name (required). Use get_project with include: [\"categories\"] to list available categories for the project."
    • changedInput schema / properties / custom_fields / description
      Previous value: -"Custom field values: [{field: {id|name}, value: \"<string>\"}]. Use get_issue_fields or get_metadata to discover available custom fields per project."New value: +"Custom field values: [{field: {id|name}, value: \"<string>\"}]. Use get_issue_schema or get_metadata to discover available custom fields per project."
    • changedInput schema / properties / fixed_in_version / description
      Previous value: -"Version in which the issue was fixed. Use get_project_versions to list available version names."New value: +"Version in which the issue was fixed. Use get_project with include: [\"versions\"] to list available version names."
    • changedInput schema / properties / handler / description
      Previous value: -"MantisBT 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."New value: +"MantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use get_project with member_query or include: [\"users\"] to look up valid login names."
    • changedInput schema / properties / priority / description
      Previous value: -"Priority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: \"normal\". Use get_issue_enums to see localized labels."New value: +"Priority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: \"normal\". Use get_issue_schema to see localized labels."
    • changedInput schema / properties / reproducibility / description
      Previous value: -"How 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."New value: +"How reliably the issue reproduces. Canonical English names: always, sometimes, random, have not tried, unable to reproduce, N/A. Use get_issue_schema to see localized labels."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Use get_issue_enums to see localized labels."New value: +"Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Use get_issue_schema to see localized labels."
    • changedInput schema / properties / target_version / description
      Previous value: -"Target fix version — version in which the issue is planned to be resolved. Use get_project_versions to list available version names."New value: +"Target fix version — version in which the issue is planned to be resolved. Use get_project with include: [\"versions\"] to list available version names."
    • changedInput schema / properties / version / description
      Previous value: -"Affected product version name. Use get_project_versions to list available version names for the project."New value: +"Affected product version name. Use get_project with include: [\"versions\"] to list available version names for the project."
  3. Changed6 schema fields changedv1.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / custom_fields / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / custom_fields / items / properties / field / additionalProperties
      Removed value: -false
    • changedInput schema / properties / custom_fields / items / required
      Previous value: -[
      -  "field"
      -]New value: +[
      +  "field",
      +  "value"
      +]
    • addedInput schema / properties / handler_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / project_id / maximum
      Added value: +9007199254740991
  4. Changed1 schema field changedv1.10.5
    • addedInput schema / properties / custom_fields
      Added value: +{
      +  "description": "Custom field values: [{field: {id|name}, value: \"<string>\"}]. Use get_issue_fields or get_metadata to discover available custom fields per project.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "field": {
      +        "additionalProperties": false,
      +        "description": "Custom field reference: { id } or { name }",
      +        "properties": {
      +          "id": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "value": {
      +        "description": "Field value as string",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "field"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  5. Addedv1.10.4
  6. Removed
  7. Changed15 schema fields changedv1.10.3
    • changedInput schema / properties / additional_information / description
      Previous value: -"Additional information about the issue. Plain text or Markdown."New value: +"Additional context or notes about the issue. Plain text or Markdown."
    • changedInput schema / properties / category / description
      Previous value: -"Category name (use get_project_categories to list available categories)"New value: +"Category name (required). Use get_project_categories to list available categories for the project."
    • changedInput schema / properties / description / description
      Previous value: -"Detailed issue description. Required — do not create issues without a description. Plain text or Markdown."New value: +"Detailed issue description (required). Do not create issues without a description. Plain text or Markdown."
    • changedInput schema / properties / fixed_in_version / description
      Previous value: -"Version name in which the issue was fixed (use get_project_versions to list available versions)"New value: +"Version in which the issue was fixed. Use get_project_versions to list available version names."
    • changedInput schema / properties / handler / description
      Previous value: -"Username (login name) of the person to assign the issue to. Alternative to handler_id — the server resolves the name to a user ID from the project members. Use get_project_users to see available users."New value: +"MantisBT 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."
    • changedInput schema / properties / handler_id / description
      Previous value: -"User ID of the person to assign the issue to"New value: +"Numeric user ID of the assignee. Alternative to the handler field — use one or the other, not both."
    • changedInput schema / properties / priority / description
      Previous value: -"Priority: canonical English name (none, low, normal, high, urgent, immediate) or localized label. Default: \"normal\". Use get_issue_enums to see all available values."New value: +"Priority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: \"normal\". Use get_issue_enums to see localized labels."
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID the issue belongs to"New value: +"Project ID the issue belongs to — use list_projects to discover project IDs"
    • changedInput schema / properties / reproducibility / description
      Previous value: -"Reproducibility: canonical English name or localized label (always, sometimes, random, have not tried, unable to reproduce, N/A). Use get_issue_enums to see all available values."New value: +"How 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."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity: canonical English name (feature, trivial, text, tweak, minor, major, crash, block) or localized label. Default: \"minor\". Use get_issue_enums to see all available values."New value: +"Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Use get_issue_enums to see localized labels."
    • changedInput schema / properties / steps_to_reproduce / description
      Previous value: -"Steps to reproduce the issue. Plain text or Markdown."New value: +"Step-by-step instructions to reproduce the issue. Plain text or Markdown."
    • changedInput schema / properties / summary / description
      Previous value: -"Issue summary/title"New value: +"Issue summary/title (required)"
    • changedInput schema / properties / target_version / description
      Previous value: -"Target version name — version in which the issue is planned to be fixed (use get_project_versions to list available versions)"New value: +"Target fix version — version in which the issue is planned to be resolved. Use get_project_versions to list available version names."
    • changedInput schema / properties / version / description
      Previous value: -"Affected product version name (use get_project_versions to list available versions)"New value: +"Affected product version name. Use get_project_versions to list available version names for the project."
    • changedInput schema / properties / view_state / description
      Previous value: -"Visibility of the issue: \"public\" (default) or \"private\""New value: +"Visibility of the issue: \"public\" (visible to all, default) or \"private\" (restricted to higher-access users)."
  8. Changed3 schema fields changedv1.5.15
    • changedInput schema / properties / priority / description
      Previous value: -"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Default: \"normal\". Call get_issue_enums to see localized labels."New value: +"Priority: canonical English name (none, low, normal, high, urgent, immediate) or localized label. Default: \"normal\". Use get_issue_enums to see all available values."
    • changedInput schema / properties / reproducibility / description
      Previous value: -"Reproducibility — must be a canonical English name: always, sometimes, random, have not tried, unable to reproduce, N/A. Call get_issue_enums to see localized labels."New value: +"Reproducibility: canonical English name or localized label (always, sometimes, random, have not tried, unable to reproduce, N/A). Use get_issue_enums to see all available values."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity name — must be a canonical English name: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Call get_issue_enums to see localized labels."New value: +"Severity: canonical English name (feature, trivial, text, tweak, minor, major, crash, block) or localized label. Default: \"minor\". Use get_issue_enums to see all available values."
  9. Changed7 schema fields changedv1.5.14
    • addedInput schema / properties / additional_information
      Added value: +{
      +  "description": "Additional information about the issue. Plain text or Markdown.",
      +  "type": "string"
      +}
    • addedInput schema / properties / fixed_in_version
      Added value: +{
      +  "description": "Version name in which the issue was fixed (use get_project_versions to list available versions)",
      +  "type": "string"
      +}
    • addedInput schema / properties / reproducibility
      Added value: +{
      +  "description": "Reproducibility — must be a canonical English name: always, sometimes, random, have not tried, unable to reproduce, N/A. Call get_issue_enums to see localized labels.",
      +  "type": "string"
      +}
    • addedInput schema / properties / steps_to_reproduce
      Added value: +{
      +  "description": "Steps to reproduce the issue. Plain text or Markdown.",
      +  "type": "string"
      +}
    • addedInput schema / properties / target_version
      Added value: +{
      +  "description": "Target version name — version in which the issue is planned to be fixed (use get_project_versions to list available versions)",
      +  "type": "string"
      +}
    • addedInput schema / properties / version
      Added value: +{
      +  "description": "Affected product version name (use get_project_versions to list available versions)",
      +  "type": "string"
      +}
    • addedInput schema / properties / view_state
      Added value: +{
      +  "description": "Visibility of the issue: \"public\" (default) or \"private\"",
      +  "enum": [
      +    "public",
      +    "private"
      +  ],
      +  "type": "string"
      +}
  10. Changed6 schema fields changedv1.5.13
    • removedInput schema / properties / description / default
      Removed value: -""
    • changedInput schema / properties / description / description
      Previous value: -"Detailed issue description"New value: +"Detailed issue description. Required — do not create issues without a description. Plain text or Markdown."
    • addedInput schema / properties / description / minLength
      Added value: +1
    • addedInput schema / properties / priority / default
      Added value: +"normal"
    • changedInput schema / properties / priority / description
      Previous value: -"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Call get_issue_enums to see localized labels."New value: +"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Default: \"normal\". Call get_issue_enums to see localized labels."
    • changedInput schema / required
      Previous value: -[
      -  "summary",
      -  "project_id",
      -  "category"
      -]New value: +[
      +  "summary",
      +  "description",
      +  "project_id",
      +  "category"
      +]
  11. Changed2 schema fields changedv1.5.9
    • changedInput schema / properties / priority / description
      Previous value: -"Priority name (e.g. \"normal\", \"high\", \"urgent\", \"immediate\", \"low\", \"none\")"New value: +"Priority name — must be a canonical English name: none, low, normal, high, urgent, immediate. Call get_issue_enums to see localized labels."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity name (e.g. \"minor\", \"major\", \"crash\", \"block\", \"feature\", \"trivial\", \"text\") — default: \"minor\""New value: +"Severity name — must be a canonical English name: feature, trivial, text, tweak, minor, major, crash, block. Default: \"minor\". Call get_issue_enums to see localized labels."
  12. First observedv1.5.6

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the description's job is to add context — and it does, describing the full return payload, the token-saving "short" response mode, and the planned default change in 2.0.0. It does not cover permission requirements, duplicate detection, or error behavior for a mutation tool, which keeps it from a 5.

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 required fields, then a numbered workflow — easy to scan. A few sentences duplicate schema content (priority "normal", severity "minor" defaults), which is mild redundancy across 17 parameters.

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?

With no output schema, the description carries the burden of explaining return values and does so for both response modes, plus the workflow for resolving category, version, and assignee names. For a 17-parameter creation tool it is largely complete, though auth/permission expectations are unstated.

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; the description adds genuine meaning by naming the four required fields, stating the priority/severity defaults, and explaining that values accept canonical English names or localized labels with get_issue_schema as the lookup. It also resolves the handler vs handler_id ambiguity. Some of this repeats schema defaults verbatim.

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?

States a specific verb and resource ("Create a new MantisBT issue") and immediately describes the returned object and its fields. The agent can distinguish this from update_issue or delete_issue without opening any schema.

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

Usage Guidelines4/5

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

Provides an explicit recommended workflow: call get_project with include: ["categories"] first, optionally add "versions", optionally use member_query for the assignee. It also gives a concrete alternative rule ("prefer the username field over handler_id when working interactively"). It stops short of naming when to choose this over siblings like update_issue or when not to create an issue, so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.