Skip to main content
Glama
testdino-hq

TestDino MCP

by testdino-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_manual_test_cases

Find and list manual test cases with flexible filters for project, status, priority, and more to support QA testing and audit.

Instructions

Search and list manual test cases with filtering capabilities. Use this to find specific manual test cases for QA testing, auditing, or test case management. Supports filtering by project, time, suite, status, priority, severity, type, layer, behavior, automation status, and tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFilter by tags. Can be a single tag or comma-separated tags. Example: 'smoke' or 'smoke,regression,login'.
timeNoFilter by time interval.
typeNoFilter by test case type.
layerNoFilter by test layer.
limitNoMaximum number of results to return (default: 10, max: 1000).
searchNoSearch term to match against title or caseId. Example: 'login' or 'TC-123'.
statusNoFilter by test case status.
suiteIdNoFilter by specific test suite ID. Use list_manual_test_suites to find suite IDs.
behaviorNoFilter by test behavior type.
priorityNoFilter by priority level.
severityNoFilter by severity level.
projectIdYesProject ID (Required). The TestDino project identifier.
automationStatusNoFilter by automation status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.0.10
    • 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"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description indicates a read-only list operation but does not disclose additional behavioral traits such as pagination, default sorting, or permissions.

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?

The description is three sentences long, front-loaded with the action and usage, and efficiently lists capabilities without fluff.

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?

Despite 13 parameters and no output schema, the description omits output format, default behavior, and sorting, leaving the agent without crucial information for effective invocation.

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 coverage is 100%, so the description adds no extra meaning beyond the parameter descriptions; the list of filter types is redundant.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies 'Search and list manual test cases with filtering capabilities,' using a specific verb-resource pair that distinguishes it from sibling tools like list_manual_test_suites.

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

Usage Guidelines4/5

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

It provides context for use cases (QA testing, auditing, test management) but does not explicitly state when not to use it or mention alternatives like get_manual_test_case for single retrieval.

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

Deploy Server

Other Tools