testit-mcp-server

list_work_items

Read-only

Lists a project's test cases, checklists, and shared steps with filters for type, state, priority, tags, name, and pagination to find and manage relevant work items.

Instructions

List work items (test cases, checklists, shared steps) of a project, with optional filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_work_items"
  }
}

Input Schema

Name	Required	Description
`name`	No	Filter by (part of) work item name.
`page`	No	1-based page number; alternative to skip. Uses "size" (default 50).
`size`	No	Page size for "page"; alias of take.
`skip`	No	Number of items to skip (offset).
`tags`	No	Tag names.
`take`	No	Max number of items to return.
`types`	No	Work item types.
`states`	No
`orderBy`	No	Sort expression, e.g. "createdDate desc".
`isDeleted`	No	Search archived (deleted) work items.
`projectId`	No	Project UUID.
`priorities`	No
`sectionIds`	No	Section UUIDs.
`isAutomated`	No
`projectName`	No	Project name (alternative to projectId).
`searchField`	No	Field name to search in.
`searchValue`	No	Value to search for in searchField.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description adds almost nothing behavioral: it does not mention pagination defaults, the fact that archived items are excluded unless isDeleted is set, or how the aliased paging parameters (page/size vs skip/take) interact.

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?

A single front-loaded sentence with no filler, parenthetical clarifying the resource domain. Nothing is redundant or misplaced.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 17-parameter tool with pagination aliases, no output schema, and only generic annotations, the description is far too thin. It omits pagination defaults, whether projectId or projectName is effectively required, and how filtering combines, leaving the agent to reverse-engineer behavior from the schema.

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 82%, so the schema already documents nearly every parameter. The description only restates that filtering is possible and repeats the three type values that the enum already supplies, adding little meaning beyond structured data. Baseline 3 is appropriate.

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?

Names a specific verb and resource ('List work items') and clarifies the domain by enumerating the types ('test cases, checklists, shared steps') plus project scoping. It does not, however, distinguish itself from siblings like search_work_items or list_autotest_work_items, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The phrase 'with optional filters' implies a filtered listing, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as search_work_items. For a tool with 17 optional parameters, the absence of any selection guidance is a real gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server