Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a new bug card

create_bug

Create a new Targetprocess bug card with a concise title and structured HTML details covering environment, issue description, reproduction steps, expected behavior, and actual behavior.

Instructions

Create a new bug card that summarizes the problem in concise, descriptive manner answering questions "What? Where? When?" and content explaining what happened in detail. NOTE: this tool does not require a user story or bug card reference. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) format the new bug inside html tags with Environment(describes where bug was found, dev, feature, review or uat Environment), Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior and Attachments sections (note: section titles should be wrapped in tags, e.g. Issue Description, step to reproduce should be wrapped in ); 2) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 3) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 4) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId; 5) IF the user specified a release by name (not ID), call "get_current_releases" to find the matching release and use its ID as releaseId;

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": {
      "title": "<title>",
      "bugContent": "<bugContent>"
    },
    "name": "create_bug"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional comma-separated tags to apply, e.g. "regression, mobile"
titleYesBug card title that summarizes the problem in concise, descriptive, and actionable manner, enabling a developer to understand the issue without opening the report
originNoWhere the bug was found, defaults to "Manual QA" if no origin was specified
teamIdNoOptional Team ID — if user gave a team name, resolve it via "get_teams" first; defaults to TP_TEAM_ID from config
projectIdNoOptional Project ID — if user gave a project name, resolve it via "get_projects" first; defaults to TP_PROJECT_ID from config
releaseIdNoOptional Release ID to assign this bug to — if user gave a release name, resolve it via "get_current_releases" first
bugContentYesBug description content, explain what happened in detail. Include expected behaviour and what actually occurred. Be specific and avoid assumptions. Clearly outline the actions needed to trigger the bug. Number each step so anyone can follow them easily
entityStateIdNoOptional Entity State ID — if user gave a state name, resolve it via "get_bug_workflows" first; defaults to "Backlog" or "To Do"
teamIterationIdNoOptional Team Iteration (sprint) ID — resolve it via "get_team_iterations" first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does well on inputs — mandatory HTML <div>/<h3>/<ol> formatting, default origin of "Manual QA", and config-sourced defaults for teamId/projectId — but says nothing about the created card's identity/return value, failure modes, or required permissions for what is clearly a mutating operation.

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

Conciseness3/5

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

The purpose sentence and the numbered workflow are front-loaded and scannable, but steps 2-5 restate resolution guidance that already appears verbatim in four separate schema parameter descriptions. That redundancy inflates length without adding information the agent doesn't already have in structured form.

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?

For a 9-parameter mutating tool with no annotations and no output schema, the definition does cover the operationally critical pieces: required fields, formatting contract, ID-resolution order, and defaults. The remaining gap is return-value and post-creation behavior, which the agent must infer.

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 description coverage is 100%, so the baseline is 3; the description earns an extra point by adding the HTML section structure requirement for bugContent (Environment, Issue Description, Steps to Reproduce, Expected, Actual, Attachments) that the schema only gestures at. It does partly duplicate the per-parameter resolution guidance already present in the schema for teamId, projectId, releaseId, and teamIterationId.

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 definition opens with a specific verb and resource ("Create a new bug card") and states the artifact must summarize What/Where/When with detailed content. The NOTE that no user story or bug card reference is required implicitly carves it apart from the card-based sibling create_bug_based_on_card, though that sibling is never named explicitly.

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?

The numbered CRITICAL WORKFLOW gives concrete preconditions: resolve team/project/sprint/release names to IDs via get_teams, get_projects, get_team_iterations, and get_current_releases before calling. What's missing is an explicit exclusion rule naming create_bug_based_on_card as the path when a card reference does exist.

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