TestDino MCP

List Manual Test Cases

list_manual_test_cases

Read-only

Search and filter manual test cases by project, suite, title or case ID, status, tags, and properties to locate the cases you need.

Instructions

Search and browse manual test cases with filters. Use suiteId to scope to a folder, search to match by title or caseId (e.g. "TC-123"), status for active/draft/deprecated, and tags for comma-separated tag filtering. Default limit is 10 — increase it if you need more results.

Input Schema

Name	Required	Description
`tags`	No	Single tag or comma-separated tags
`time`	No	e.g. "last 1 hour", "Yesterday", "last 7 days"
`type`	No	Type. Values come from Project Settings → Test Case Properties. Defaults: Smoke, Regression, Functional, Integration, E2E, API, Unit, Performance, Security, Accessibility, Usability, Compatibility, Acceptance, Exploratory, Other.
`layer`	No	Layer. Values come from Project Settings → Test Case Properties. Defaults: E2E, API, Unit, Not Set.
`limit`	No	Default 10
`search`	No	Match title or caseId
`status`	No
`suiteId`	No
`behavior`	No	Behavior. Values come from Project Settings → Test Case Properties. Defaults: Positive, Negative, Destructive, Not Set.
`priority`	No	Priority. Values come from Project Settings → Test Case Properties. Defaults: Critical, High, Medium, Low, Not Set.
`severity`	No	Severity. Values come from Project Settings → Test Case Properties. Defaults: Blocker, Critical, Major, Normal, Minor, Trivial, Not Set.
`projectId`	Yes	Project ID
`automationStatus`	No	Automation status. Values come from Project Settings → Test Case Properties. Defaults: Manual, Automated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedv2.2.0Oct 14, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / automationStatus / description

Previous value: -"Filter by automation status."New value: +"Automation status. Values come from Project Settings → Test Case Properties. Defaults: Manual, Automated."

removedInput schema / properties / automationStatus / enum

Removed value: -[
-  "Manual",
-  "Automated",
-  "To be automated"
-]

changedInput schema / properties / behavior / description

Previous value: -"Filter by test behavior type."New value: +"Behavior. Values come from Project Settings → Test Case Properties. Defaults: Positive, Negative, Destructive, Not Set."

removedInput schema / properties / behavior / enum

Removed value: -[
-  "positive",
-  "negative",
-  "destructive",
-  "Not set"
-]

changedInput schema / properties / layer / description

Previous value: -"Filter by test layer."New value: +"Layer. Values come from Project Settings → Test Case Properties. Defaults: E2E, API, Unit, Not Set."

removedInput schema / properties / layer / enum

Removed value: -[
-  "e2e",
-  "api",
-  "unit",
-  "not set"
-]

removedInput schema / properties / limit / default
```
Removed value: -10
```

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results to return (default: 10, max: 1000)."New value: +"Default 10"

addedInput schema / properties / limit / maximum
```
Added value: +1000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / priority / description

Previous value: -"Filter by priority level."New value: +"Priority. Values come from Project Settings → Test Case Properties. Defaults: Critical, High, Medium, Low, Not Set."

removedInput schema / properties / priority / enum

Removed value: -[
-  "high",
-  "medium",
-  "low",
-  "Not set"
-]

changedInput schema / properties / projectId / description

Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"Project ID"

changedInput schema / properties / search / description

Previous value: -"Search term to match against title or caseId. Example: 'login' or 'TC-123'."New value: +"Match title or caseId"

changedInput schema / properties / severity / description

Previous value: -"Filter by severity level."New value: +"Severity. Values come from Project Settings → Test Case Properties. Defaults: Blocker, Critical, Major, Normal, Minor, Trivial, Not Set."

removedInput schema / properties / severity / enum

Removed value: -[
-  "Blocker",
-  "critical",
-  "major",
-  "Normal",
-  "minor",
-  "trivial",
-  "Not set"
-]

removedInput schema / properties / status / description
```
Removed value: -"Filter by test case status."
```

removedInput schema / properties / suiteId / description

Removed value: -"Filter by specific test suite ID. Use list_manual_test_suites to find suite IDs."

changedInput schema / properties / tags / description

Previous value: -"Filter by tags. Can be a single tag or comma-separated tags. Example: 'smoke' or 'smoke,regression,login'."New value: +"Single tag or comma-separated tags"

changedInput schema / properties / time / description

Previous value: -"Filter by time interval."New value: +"e.g. \"last 1 hour\", \"Yesterday\", \"last 7 days\""

removedInput schema / properties / time / enum

Removed value: -[
-  "last 1 hour",
-  "Last 5 hours",
-  "Yesterday",
-  "last 7 days"
-]

changedInput schema / properties / type / description

Previous value: -"Filter by test case type."New value: +"Type. Values come from Project Settings → Test Case Properties. Defaults: Smoke, Regression, Functional, Integration, E2E, API, Unit, Performance, Security, Accessibility, Usability, Compatibility, Acceptance, Exploratory, Other."

removedInput schema / properties / type / enum

Removed value: -[
-  "functional",
-  "smoke",
-  "regression",
-  "security",
-  "performance",
-  "e2e",
-  "Integration",
-  "API",
-  "Unit",
-  "Accessability",
-  "Compatibility",
-  "Acceptance",
-  "Exploratory",
-  "Usability",
-  "Other"
-]

Changed13 schema fields changedv1.0.10May 19, 2026

changedInput schema / properties / automationStatus / enum

Previous value: -[
-  "automated",
-  "manual",
-  "not_automated"
-]New value: +[
+  "Manual",
+  "Automated",
+  "To be automated"
+]

changedInput schema / properties / behavior / enum

Previous value: -[
-  "positive",
-  "negative",
-  "destructive"
-]New value: +[
+  "positive",
+  "negative",
+  "destructive",
+  "Not set"
+]

removedInput schema / properties / isFlaky

Removed value: -{
-  "description": "Filter test cases marked as flaky. Set to true to show only flaky tests, false for non-flaky.",
-  "type": "boolean"
-}

changedInput schema / properties / layer / enum

Previous value: -[
-  "e2e",
-  "api",
-  "unit"
-]New value: +[
+  "e2e",
+  "api",
+  "unit",
+  "not set"
+]

changedInput schema / properties / limit / default
```
Previous value: -50New value: +10
```

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results to return (default: 50, max: 1000)."New value: +"Maximum number of results to return (default: 10, max: 1000)."

changedInput schema / properties / priority / enum

Previous value: -[
-  "critical",
-  "high",
-  "medium",
-  "low"
-]New value: +[
+  "high",
+  "medium",
+  "low",
+  "Not set"
+]

changedInput schema / properties / search / description

Previous value: -"Search term to match against title, description, or caseId. Example: 'login' or 'TC-123'."New value: +"Search term to match against title or caseId. Example: 'login' or 'TC-123'."

changedInput schema / properties / severity / enum

Previous value: -[
-  "critical",
-  "major",
-  "minor",
-  "trivial"
-]New value: +[
+  "Blocker",
+  "critical",
+  "major",
+  "Normal",
+  "minor",
+  "trivial",
+  "Not set"
+]

changedInput schema / properties / status / enum

Previous value: -[
-  "actual",
-  "draft",
-  "deprecated"
-]New value: +[
+  "active",
+  "draft",
+  "deprecated"
+]

changedInput schema / properties / tags / description

Previous value: -"Filter by tags (comma-separated list). Example: 'smoke,regression' or 'critical'."New value: +"Filter by tags. Can be a single tag or comma-separated tags. Example: 'smoke' or 'smoke,regression,login'."

addedInput schema / properties / time

Added value: +{
+  "description": "Filter by time interval.",
+  "enum": [
+    "last 1 hour",
+    "Last 5 hours",
+    "Yesterday",
+    "last 7 days"
+  ],
+  "type": "string"
+}

changedInput schema / properties / type / enum

Previous value: -[
-  "functional",
-  "smoke",
-  "regression",
-  "security",
-  "performance",
-  "e2e"
-]New value: +[
+  "functional",
+  "smoke",
+  "regression",
+  "security",
+  "performance",
+  "e2e",
+  "Integration",
+  "API",
+  "Unit",
+  "Accessability",
+  "Compatibility",
+  "Acceptance",
+  "Exploratory",
+  "Usability",
+  "Other"
+]

First observedJan 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's main addition is the default limit of 10 and the advice to raise it, which is genuinely useful behavioral context. It says nothing about ordering, pagination beyond the limit, or the shape of results.

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?

Four tight sentences, front-loaded with the core action and then the highest-value filters. Every sentence carries information; no filler or repetition of the title.

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 13-parameter read-only listing tool with no output schema, the description plus the rich schema docs cover what an agent needs to invoke it correctly. The main gap is sibling disambiguation and any indication of result ordering or total count.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 85%, so the baseline is 3, but the description adds real value: it explains suiteId scopes to a folder, that search matches title or caseId with a concrete 'TC-123' example, and that tags are comma-separated. It leaves type/layer/behavior/priority/severity/time to the 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?

Names a specific verb and resource: search and browse manual test cases with filters. Clear what the tool returns, but it never differentiates itself from the similarly named sibling list_testcase, which an agent could easily confuse with this one.

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 filter-usage guidance (scope with suiteId, match with search, filter by status/tags) and a practical nudge to raise the limit. However there is no when-to-use-this-vs-alternatives guidance against list_testcase, list_manual_test_suites, or get_manual_test_case.

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

Deploy Server

List Manual Test Cases

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools