List per-feature success metrics

featuremetric.listReadsOnly looks things up; never changes your workspace.

What it does

Lists the success metrics attached to features in the connected workspace, newest first. A feature metric is a number that shows whether one feature is working for users, such as checkout conversion rate for a "Checkout" feature. For whole-product numbers (like weekly active users) use productkpi.list. Use it to see what is measured for a feature, or to find the id for metric.observe. Returns {items: [{id, uri, featureId, name, unit, direction, baseline, target, status}], totalItems, page, pageSize}. Gotcha: the featureId filter is applied only to the rows on the requested page, and totalItems then counts just those matches, so with many metrics use pageSize 100 and check each page. Read-only. Recorded values over time are in the resource testmaze://metric-observations/{spaceId}/feature/{id}.

Ask your agent

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

  • “How are we measuring whether checkout is working?”
  • “List the success metrics for the onboarding feature”

Inputs

NameTypeDescription
featureId
optional
stringOnly show metrics for this feature: its id from feature.list. Filters within the returned page only.
page
optional
integerPage number, starting at 1 (default 1).
pageSize
optional
integerRows per page, 1 to 100 (default 20).

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "featuremetric.list",
    "arguments": {
      "featureId": "<featureId>"
    }
  }
}

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.