Edit a feature

feature.updateChanges dataCreates, updates or deletes something in your workspace.

What it does

Changes a feature or sub-feature of the connected workspace: title (unique across features and stories in the workspace), description, priority, parent feature, owner, target release date, rollout percentage, feature flag key, or status (INACTIVE hides it). Send only the fields to change; null clears an optional field. Its test cases, stories and results are not touched. The lifecycle stage and release have their own tools (feature.set_lifecycle, feature.set_release); stories are edited with userstory.update. Get the id from feature.list. Returns {success, data: the updated feature, uri}.

Ask your agent

You don’t call feature.update yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:

  • “Rename the Checkout feature to "Guest checkout"”
  • “Make password reset a P0”
  • “Checkout now ships on 30 June, update its target date”

Inputs

NameTypeDescription
suiteId
required
stringId of the feature or sub-feature (the id from feature.list).
title
optional
stringNew title, unique across features and stories in the workspace.
description
optional
string | nullNew description; null clears it.
priority
optional
enumP0 = critical; P1 = high; P2 = normal; P3 = nice to have.
Allowed: P0P1P2P3
parentFeatureId
optional
string | nullId of the bigger feature it belongs to (from feature.list); null detaches it.
featureOwnerId
optional
string | nullUser id of the person responsible (a member of this workspace); null clears it.
targetReleaseDate
optional
string | nullYYYY-MM-DD; null clears it.
rolloutPercentage
optional
integer | nullShare of users who get it, 0 to 100; null clears it.
featureFlagKey
optional
string | nullFeature flag that switches it on; null clears it.
status
optional
enumACTIVE, or INACTIVE to hide it.
Allowed: ACTIVEINACTIVE

The MCP call

What the agent’s MCP client sends (placeholders in angle brackets):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "feature.update",
    "arguments": {
      "suiteId": "<suiteId>"
    }
  }
}

Connect your agent

npx -y @testmaze/mcp init tmt_xxx
claude mcp add tm --scope project -- npx -y @testmaze/mcp

Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.