Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Update a user story card

update_user_story

Modify a Targetprocess user story card by ID, changing only specified fields such as title, description, state, team, project, sprint, feature, or tags.

Instructions

Update a user story 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 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_user_story_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;

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

Input Schema

NameRequiredDescriptionDefault
idYesUser story card ID (e.g. 145789)
tagsNoOptional comma-separated tags to apply, e.g. "regression, mobile"
titleNoUpdated user story title
teamIdNoOptional Team ID — if user gave a team name, resolve it via "get_teams" first
featureIdNoOptional Feature ID — moves this user story to the specified feature
projectIdNoOptional Project ID — if user gave a project name, resolve it via "get_projects" first
descriptionNoUpdated user story description (format as HTML)
entityStateIdNoOptional Entity State ID — if user gave a state name, resolve it via "get_user_story_workflows" first
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.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It usefully establishes partial-update semantics and the prerequisite lookups, but says nothing about required permissions, whether changes are reversible or audited, how unspecified fields are treated, or what the call returns — real gaps for a mutation tool with zero annotation coverage.

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?

The numbered workflow is front-loaded after a one-line purpose statement and each step earns its place. Minor waste in the opener 'with data provided from user input', which conveys nothing the rest does not.

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, 1-required mutation tool with no output schema and no annotations, the definition covers the highest-risk confusion (name-vs-ID) and partial-update behavior. It stops short of describing the response, failure modes, or side effects such as reassigning a card to a different feature/iteration.

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 the schema already documents every field, including the 'resolve via get_teams/get_projects/...' hints, so the description largely restates structured data. Its only added semantic is the partial-update rule (send only the fields the user wants changed), which is worthwhile but thin against a fully documented schema.

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 user story card') plus the partial-update intent ('pass only the fields that user wants to update'), which an agent can distinguish from update_bug/update_epic/update_feature by resource name. It does not explicitly contrast with update_user_story_state, so sibling differentiation is implicit rather than stated.

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 conditional workflow gives clear, actionable preconditions: resolve team/project/state/iteration names to IDs via get_teams, get_projects, get_user_story_workflows, and get_team_iterations respectively. It does not, however, say when to prefer the state-only sibling update_user_story_state over setting entityStateId here, leaving one genuine alternative unaddressed.

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