Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Update a feature card

update_feature

Update a Targetprocess feature card with only the fields the user wants to change, such as title, description, tags, epic, team, project, release, or sprint.

Instructions

Update a feature card with data provided 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 an epic by name (not ID), resolve the epic ID first; 2) IF the user specified a release by name (not ID), call "get_current_releases" to resolve the release ID; 3) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 4) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 5) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId;

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_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFeature card ID (e.g. 145636)
tagsNoOptional comma-separated tags to apply, e.g. "regression, mobile"
titleNoUpdated feature title
epicIdNoOptional Epic ID — moves this feature to the specified epic
teamIdNoOptional Team ID — if user gave a team name, resolve it via "get_teams" first
projectIdNoOptional Project ID — if user gave a project name, resolve it via "get_projects" first
releaseIdNoOptional Release ID to link this feature to
descriptionNoUpdated feature description (format as HTML)
entityStateIdNoOptional Entity State ID — ask the user for the exact ID if given a state name; no dedicated feature-workflow lookup tool exists yet
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.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses partial-update/patch semantics and the name-to-ID prerequisite chain, which is valuable, but says nothing about permissions, what happens when an ID is invalid, whether changes are reversible, or what the response contains for a mutation tool with 10 fields.

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 key constraint is front-loaded, but 'with data provided from user input' is filler and the five-step workflow largely duplicates the resolution hints already present in the schema descriptions, making the definition longer than it needs to be.

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 10-parameter mutation with full schema coverage and no output schema, the description covers the two things an agent most needs to know: only send changed fields, and resolve referenced names to IDs first. Gaps around failure modes and permissions are real but modest given the schema's detail.

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 coverage is 100%, so the schema already documents every parameter, including the resolve-via-lookup hints on teamId, projectId, releaseId, and teamIterationId. The description mostly restates the same resolution guidance in workflow form, adding ordering but little new per-parameter meaning.

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 description states a specific verb and resource ('Update a feature card') and the resource name separates it from siblings like update_epic, update_user_story, and update_bug. It doesn't explicitly contrast with those siblings, but the resource distinction is unambiguous.

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?

It gives an explicit constraint ('pass only the fields that user wants to update') and a conditional, ordered workflow for resolving display names to IDs via get_teams, get_projects, get_current_releases, and get_team_iterations. An agent knows exactly what prerequisite calls to make before invoking this tool.

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