Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a new user story

create_user_story

Creates a Targetprocess user story from a title plus optional project, feature, release, tags, and sprint. Resolve named sprint to iteration ID first to link it correctly.

Instructions

Create a new user story in Targetprocess. CRITICAL WORKFLOW: Before calling this tool, 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": {
      "title": "<title>"
    },
    "name": "create_user_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional comma-separated tags to apply, e.g. "regression, mobile"
titleYesUser story title
teamIdNoOptional Team ID — defaults to TP_TEAM_ID from config
featureIdNoOptional Feature ID to link this user story to (e.g. 145636)
projectIdNoOptional Project ID — defaults to TP_PROJECT_ID from config
releaseIdNoOptional Release ID to link this user story to (e.g. 145200)
descriptionNoOptional user story description (when provided, format as HTML)
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?

No annotations are supplied, so the description carries the full burden. It does disclose a non-obvious behavioral requirement (resolving iteration names to IDs before the call), which is valuable. But it says nothing about permissions, what happens when a referenced featureId/releaseId is invalid, or what the call returns after creating the story.

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?

Two short, front-loaded blocks with no wasted wording; the critical prerequisite is called out before the agent commits to a call. The all-caps 'CRITICAL WORKFLOW' label is slightly heavy-handed but does not cost comprehension.

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 an eight-parameter creation tool with no output schema, the description should say what comes back (e.g., the new story ID) and how it differs from create_formatted_user_story. The ID-resolution workflow is covered, but those two gaps keep it at minimum-viable completeness.

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 all eight parameters are already documented, including the teamIterationId resolution hint and config defaults for teamId/projectId. The description adds only the workflow framing around teamIterationId, which is largely a restatement of the schema note. Baseline 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: 'Create a new user story in Targetprocess.' An agent knows exactly what is being made. It does not, however, distinguish itself from the sibling create_formatted_user_story, so the choice between the two is left to inference.

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 an explicit conditional prerequisite: if the user names a sprint/iteration, first call get_team_iterations and pass its ID as teamIterationId. That is real routing guidance to a named sibling. It stops short of covering when to use this tool versus create_formatted_user_story or when not to use it at all.

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