TestOps MCP Server

list-test-cases

List test cases in a project by project ID, with optional text search and pagination.

Instructions

List test cases in a project. Use list-projects first to get projectId. Supports text search.

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": {
      "projectId": "<projectId>"
    },
    "name": "list-test-cases"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (0-based)
`size`	No	Page size
`search`	No	Text search query
`projectId`	Yes	Project ID (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Jul 30, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description bears full burden. It states a read operation but does not disclose pagination behavior, default sorting, rate limits, or what happens when no search is provided. The schema indicates pagination but description ignores this.

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?

Two front-loaded sentences with no redundancy. Every sentence adds value: purpose, prerequisite, and capability.

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?

Covers basic purpose and a prerequisite, but lacks details on pagination, default behavior, and return format. For a list tool with no output schema, more context is needed.

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 baseline is 3. Description adds minimal value: only 'text search' reiterates the search parameter. Pagination parameters (page, size) are not explained beyond schema.

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?

Clearly states it lists test cases in a project. The text search capability is mentioned, but it does not explicitly differentiate from sibling tool 'search-test-cases' which might have similar functionality.

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?

Provides a useful prerequisite ('Use list-projects first to get projectId') and mentions text search, but lacks guidance on when to use this tool versus alternatives like 'search-test-cases' or when not to use it.

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

Deploy Server