Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a new feature

create_feature

Creates a Targetprocess feature from a fully pre-written HTML description for legacy cases where structured templates are explicitly declined.

Instructions

DEPRECATED — use "create_formatted_feature" instead for all new features. Only call this tool when you have a fully pre-written HTML description and the user has explicitly opted out of the structured template.

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

Input Schema

NameRequiredDescriptionDefault
titleYesFeature title
epicIdNoOptional Epic ID to link this feature to (e.g. 145636)
teamIdNoOptional Team ID — defaults to TP_TEAM_ID from config
projectIdNoOptional Project ID — defaults to TP_PROJECT_ID from config
releaseIdNoOptional Release ID to link this feature to (e.g. 145200)
descriptionNoOptional feature description (when provided, format as HTML)

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?

There are no annotations, so the description must carry the behavioral burden. It discloses deprecation and the opt-out condition, which is useful context, but it does not describe the mutation's side effects, authorization needs, or what specifically gets created.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the most important information: deprecated status and replacement tool. Every sentence earns its 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?

Given the deprecated status and rich schema coverage, the description is sufficient for routing the agent away from this tool. However, for a create mutation with no annotations or output schema, it lacks operational details about what happens when the tool is actually invoked.

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%, so the schema already documents all six parameters and the HTML formatting requirement for description. The description reinforces the HTML condition but adds little parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is primarily a deprecation notice and does not explicitly state that this tool creates a feature. Its purpose is implied by the tool name/title and by the reference to the replacement tool, but the description itself never gives a direct verb-plus-resource statement.

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?

The description explicitly names the preferred alternative, create_formatted_feature, and gives the exact conditions for calling this deprecated tool: a fully pre-written HTML description and explicit user opt-out of the structured template. This is strong when-to-use / when-not-to-use guidance.

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