Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Update a bug card

update_bug

Update Targetprocess bug fields such as title, description, state, team, project, iteration, release, origin, and tags using only the values the user wants changed.

Instructions

Update a bug card with data proded from user input. NOTE: pass only the fields that user wants to update. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 2) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 3) IF the user specified a state by name (not ID), call "get_bug_workflows" to find the matching state and use its ID as entityStateId; 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": {
      "id": "<id>"
    },
    "name": "update_bug"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBug card ID (e.g. 145789)
tagsNoOptional comma-separated tags to apply, e.g. "regression, mobile"
titleNoBug 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"
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
bugContentNoBug 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"
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.5/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 discloses partial-update semantics and prerequisites for ID resolution, which is useful. It says nothing about permissions/auth, what happens to unspecified fields (implicit only), error behavior, or what the tool returns after a mutation.

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 definition is front-loaded with purpose then a numbered workflow, which is readable. But the five-step list duplicates information already present in the schema field descriptions, and the opening sentence contains a typo ("proded"), so several lines do not earn their place.

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

Completeness3/5

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

For a 10-parameter mutation tool with no annotations and no output schema, the description covers the hardest part (ID resolution) but omits return values, failure modes, and confirmation expectations. Adequate as a minimum but leaves real gaps an agent would want filled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and every parameter already documents its own resolution rule (e.g. teamId: "resolve it via get_teams first"). The description's workflow steps largely restate those schema descriptions rather than adding new meaning, so the baseline of 3 applies.

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 ("Update a bug card") which cleanly distinguishes it from update_epic, update_feature, update_user_story. However, the remainder of the sentence ("with data proded from user input") is garbled and adds nothing to purpose.

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?

Gives explicit when-to-use guidance in the form of a conditional workflow mapping five name-to-ID resolution cases to specific sibling tools (get_teams, get_projects, get_bug_workflows, get_team_iterations, get_current_releases). It also states the partial-update rule ("pass only the fields that user wants to update"). It stops short of telling the agent when not to use this tool (e.g. vs create_bug or the other update_* tools).

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