Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Update an epic

update_epic

Modify an existing Targetprocess Epic by specifying only the fields to change, such as title, description, project ID, or release link.

Instructions

Update a Targetprocess Epic. Pass only the fields to change.

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

Input Schema

NameRequiredDescriptionDefault
idYesEpic ID (e.g. 148813)
titleNoUpdated epic title
projectIdNoOptional Project ID
releaseIdNoOptional Release ID to link this epic to
descriptionNoUpdated epic description (format as HTML)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.5/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 burden. 'Pass only the fields to change' usefully discloses partial-update semantics rather than replacement semantics, which is real behavioral value. It says nothing about permissions, whether omitted fields are preserved, whether the change is reversible, or what is returned on success.

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 sentences, front-loaded with the verb and resource, then the key operational rule. Nothing is wasted, though it is arguably too terse for a mutation tool operating without annotations.

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 five-parameter mutation tool with no output schema, the description covers the essential call-shape decision (partial update). Missing pieces are permission requirements and confirmation of what happens to fields that are omitted, which an agent must infer.

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 each field (id, title, projectId, releaseId, description) is already documented. The description's partial-update instruction adds cross-parameter meaning beyond the schema, but it explains no individual parameter further; the correct baseline here is 3.

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 Targetprocess Epic'), which is enough to distinguish it from sibling mutators on other entities such as update_bug or update_feature. It does not explicitly differentiate from create_epic or get_epic_content beyond the verb, but the intent 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description presumes an existing epic identified by id and tells the caller to send a sparse payload. There is no statement of preconditions (must the epic already exist, does it need a project context?) or of when to prefer another tool such as create_epic.

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