Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Update a user story card sub state

update_user_story_state

Update a Targetprocess user story's workflow state using its ID, resolved team and team assignment IDs, and an entity state ID. Resolve these IDs via user story content and workflow lookups first.

Instructions

Update a user story card sub state with data provided from user input. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) call "get_user_story_content" to find the matching team, assigned (responsible) team and their IDs 1) call "get_user_story_workflows" to find matching state and use its ID in entityStateId

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

Input Schema

NameRequiredDescriptionDefault
idYesUser story card ID (e.g. 145789)
teamIdNoTeam ID, resolve it via "get_teams" first
entityStateIdNoEntity state ID, resolve it via "get_user_story_workflows" first
teamAssignmentIdNoTeam Assignment ID, resolve it via "get_user_story_content" 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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a genuine behavioral trait: the call is dependent on IDs resolved by other endpoints, and it implies a mutation of card state. It says nothing about permissions, reversibility, what happens to the card's current state, or the effect of omitting the optional team parameters.

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?

Short and front-loaded with the critical workflow before the details. Points off for the filler phrase "with data provided from user input" and the broken list numbering.

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 mutation tool with no annotations and no output schema, the description covers the ID-resolution path but omits required-vs-optional expectations (only id is required) and what the tool returns or changes. An agent still cannot predict the outcome of a successful call.

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 each parameter already names the tool that resolves it, so the description largely repeats schema content rather than adding meaning. It does reinforce that get_user_story_content yields both the team and the responsible team plus their IDs, which slightly clarifies the id/teamId/teamAssignmentId relationship.

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 sub state"), which distinguishes it from the broader sibling update_user_story. However, "sub state" is never defined, so an agent unfamiliar with the domain cannot tell whether this is a workflow state, a status, or a sub-status.

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 mandatory pre-call workflow naming two sibling tools and what to extract from each (team/assigned team IDs, matching state ID). It stops short of saying when NOT to use this tool versus update_user_story, and the duplicated "1)" numbering makes the ordering ambiguous (is (1) a prerequisite of (1)?).

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