TestDino MCP

get_testcase_details

Retrieve detailed test case information including error messages, code snippets, test steps, console logs, and artifacts to debug test failures effectively.

Instructions

Get detailed information about a specific test case. You can identify the test case in two ways: 1) By testcase_id (can be used alone), or 2) By testcase_name combined with testrun_id (required because test cases can have the same name across different test runs). Returns error message, code snippet, file location, test steps per attempt, console logs, and artifacts (screenshots, videos, traces). Use steps_filter='failed_only' to return only steps that errored, stripping passing setup/hook steps. Use this to debug why a test failed or understand how it executed. Example: 'Get test case details for "Verify user can logout and login" in testrun #43'.

Input Schema

TableJSON Schema

Name	Required	Description
`by_title`	No	(deprecated — use testcase_name) Test case title (partial match, case-insensitive). Retained for backward compatibility.
`projectId`	Yes	Project ID (Required). The TestDino project identifier.
`testcaseid`	No	(deprecated — use testcase_id) Test case ID. Retained for backward compatibility.
`testrun_id`	No	Single test run ID to filter results. Example: 'test_run_6901b2abc6b187e63f536a6b'.
`testcase_id`	No	Test case ID. Can be used alone to get test case details. Example: 'test_case_123'.
`by_fulltitle`	No	Full test case title including suite path (partial match, case-insensitive). Example: 'auth.spec.js > Login > Verify user can logout and login'.
`steps_filter`	No	Filter steps in each attempt. Use 'failed_only' to return only steps with errors, stripping passing setup and hook steps.
`by_testrun_id`	No	(deprecated — use testrun_id) Single test run ID to filter results. Retained for backward compatibility.
`history_limit`	No	Max number of history entries to return (max: 100, default: 10).
`testcase_name`	No	Test case title (partial match, case-insensitive). Must be combined with testrun_id when used alone. Example: 'Verify user can logout and login'.
`by_testrun_ids`	No	Multiple test run IDs (comma-separated, max 20). Example: 'test_run_abc,test_run_def'.
`include_history`	No	Include historical executions of the same test case when searching by name. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedv2.0.2Aug 12, 2026

removedInput schema / properties / by_code_snippet

Removed value: -{
-  "description": "Search in error code snippets (partial match, case-insensitive).",
-  "type": "string"
-}

removedInput schema / properties / by_error_message

Removed value: -{
-  "description": "Search in error messages (partial match, case-insensitive). Example: 'Timeout 15000ms exceeded'.",
-  "type": "string"
-}

addedInput schema / properties / by_fulltitle

Added value: +{
+  "description": "Full test case title including suite path (partial match, case-insensitive). Example: 'auth.spec.js > Login > Verify user can logout and login'.",
+  "type": "string"
+}

removedInput schema / properties / by_status

Removed value: -{
-  "description": "Filter by test case status.",
-  "enum": [
-    "passed",
-    "failed",
-    "skipped",
-    "flaky"
-  ],
-  "type": "string"
-}

addedInput schema / properties / by_testrun_id

Added value: +{
+  "description": "(deprecated — use testrun_id) Single test run ID to filter results. Retained for backward compatibility.",
+  "type": "string"
+}

addedInput schema / properties / by_testrun_ids

Added value: +{
+  "description": "Multiple test run IDs (comma-separated, max 20). Example: 'test_run_abc,test_run_def'.",
+  "type": "string"
+}

addedInput schema / properties / by_title

Added value: +{
+  "description": "(deprecated — use testcase_name) Test case title (partial match, case-insensitive). Retained for backward compatibility.",
+  "type": "string"
+}

removedInput schema / properties / counter

Removed value: -{
-  "description": "Test run counter number. Alternative to testrun_id to identify the test run. Example: 43.",
-  "type": "number"
-}

removedInput schema / properties / get_all

Removed value: -{
-  "default": false,
-  "description": "Return all matching results up to 1000 (default: false).",
-  "type": "boolean"
-}

changedInput schema / properties / history_limit / description

Previous value: -"Max number of history entries to return (default: 10)."New value: +"Max number of history entries to return (max: 100, default: 10)."

removedInput schema / properties / include_artifacts

Removed value: -{
-  "default": false,
-  "description": "Include all artifacts (screenshots, traces, videos, attachments) with authenticated URLs. Default: false.",
-  "type": "boolean"
-}

removedInput schema / properties / include_attachments

Removed value: -{
-  "default": false,
-  "description": "Include all attachment metadata from test attempts. Default: false.",
-  "type": "boolean"
-}

removedInput schema / properties / include_screenshots

Removed value: -{
-  "default": false,
-  "description": "Include screenshot URLs from test attempts. Default: false.",
-  "type": "boolean"
-}

removedInput schema / properties / include_traces

Removed value: -{
-  "default": false,
-  "description": "Include Playwright trace links from test attempts. Default: false.",
-  "type": "boolean"
-}

removedInput schema / properties / include_videos

Removed value: -{
-  "default": false,
-  "description": "Include video recording URLs from test attempts. Default: false.",
-  "type": "boolean"
-}

removedInput schema / properties / limit

Removed value: -{
-  "description": "Max results to return (default: 1 for ID lookup, 50 for search, max: 1000).",
-  "type": "number"
-}

removedInput schema / properties / page

Removed value: -{
-  "default": 1,
-  "description": "Page number for pagination (default: 1).",
-  "type": "number"
-}

removedInput schema / properties / sort_by

Removed value: -{
-  "description": "Sort results by field (default: startTime).",
-  "enum": [
-    "startTime",
-    "duration"
-  ],
-  "type": "string"
-}

removedInput schema / properties / sort_order

Removed value: -{
-  "description": "Sort direction (default: desc).",
-  "enum": [
-    "asc",
-    "desc"
-  ],
-  "type": "string"
-}

removedInput schema / properties / testcase_fulltitle

Removed value: -{
-  "description": "Full test case title including suite path (partial match, case-insensitive). Example: 'auth.spec.js > Login > Verify user can logout and login'.",
-  "type": "string"
-}

changedInput schema / properties / testcase_name / description

Previous value: -"Test case title (partial match, case-insensitive). Must be combined with testrun_id or counter when used alone. Example: 'Verify user can logout and login'."New value: +"Test case title (partial match, case-insensitive). Must be combined with testrun_id when used alone. Example: 'Verify user can logout and login'."

addedInput schema / properties / testcaseid

Added value: +{
+  "description": "(deprecated — use testcase_id) Test case ID. Retained for backward compatibility.",
+  "type": "string"
+}

removedInput schema / properties / testrun_ids

Removed value: -{
-  "description": "Multiple test run IDs (comma-separated, max 20). Example: 'test_run_abc,test_run_def'.",
-  "type": "string"
-}

removedInput schema / properties / testsuite_id

Removed value: -{
-  "description": "Filter by test suite ID.",
-  "type": "string"
-}

Changed22 schema fields changedv1.0.10May 19, 2026

addedInput schema / properties / by_code_snippet

Added value: +{
+  "description": "Search in error code snippets (partial match, case-insensitive).",
+  "type": "string"
+}

addedInput schema / properties / by_error_message

Added value: +{
+  "description": "Search in error messages (partial match, case-insensitive). Example: 'Timeout 15000ms exceeded'.",
+  "type": "string"
+}

addedInput schema / properties / by_status

Added value: +{
+  "description": "Filter by test case status.",
+  "enum": [
+    "passed",
+    "failed",
+    "skipped",
+    "flaky"
+  ],
+  "type": "string"
+}

changedInput schema / properties / counter / description

Previous value: -"Test run counter number. Required when using testcase_name (if testrun_id is not provided) to specify which test run's test case you want. Example: 43."New value: +"Test run counter number. Alternative to testrun_id to identify the test run. Example: 43."

addedInput schema / properties / get_all

Added value: +{
+  "default": false,
+  "description": "Return all matching results up to 1000 (default: false).",
+  "type": "boolean"
+}

addedInput schema / properties / history_limit

Added value: +{
+  "default": 10,
+  "description": "Max number of history entries to return (default: 10).",
+  "type": "number"
+}

addedInput schema / properties / include_artifacts

Added value: +{
+  "default": false,
+  "description": "Include all artifacts (screenshots, traces, videos, attachments) with authenticated URLs. Default: false.",
+  "type": "boolean"
+}

addedInput schema / properties / include_attachments

Added value: +{
+  "default": false,
+  "description": "Include all attachment metadata from test attempts. Default: false.",
+  "type": "boolean"
+}

addedInput schema / properties / include_history

Added value: +{
+  "default": false,
+  "description": "Include historical executions of the same test case when searching by name. Default: false.",
+  "type": "boolean"
+}

addedInput schema / properties / include_screenshots

Added value: +{
+  "default": false,
+  "description": "Include screenshot URLs from test attempts. Default: false.",
+  "type": "boolean"
+}

addedInput schema / properties / include_traces

Added value: +{
+  "default": false,
+  "description": "Include Playwright trace links from test attempts. Default: false.",
+  "type": "boolean"
+}

addedInput schema / properties / include_videos

Added value: +{
+  "default": false,
+  "description": "Include video recording URLs from test attempts. Default: false.",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Max results to return (default: 1 for ID lookup, 50 for search, max: 1000).",
+  "type": "number"
+}

addedInput schema / properties / page

Added value: +{
+  "default": 1,
+  "description": "Page number for pagination (default: 1).",
+  "type": "number"
+}

addedInput schema / properties / sort_by

Added value: +{
+  "description": "Sort results by field (default: startTime).",
+  "enum": [
+    "startTime",
+    "duration"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sort_order

Added value: +{
+  "description": "Sort direction (default: desc).",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

addedInput schema / properties / steps_filter

Added value: +{
+  "description": "Filter steps in each attempt. Use 'failed_only' to return only steps with errors, stripping passing setup and hook steps.",
+  "enum": [
+    "failed_only"
+  ],
+  "type": "string"
+}

addedInput schema / properties / testcase_fulltitle

Added value: +{
+  "description": "Full test case title including suite path (partial match, case-insensitive). Example: 'auth.spec.js > Login > Verify user can logout and login'.",
+  "type": "string"
+}

changedInput schema / properties / testcase_name / description

Previous value: -"Test case name/title. Must be combined with either testrun_id or counter to identify which test run's test case you want. Example: 'Verify user can logout and login'."New value: +"Test case title (partial match, case-insensitive). Must be combined with testrun_id or counter when used alone. Example: 'Verify user can logout and login'."

changedInput schema / properties / testrun_id / description

Previous value: -"Test run ID. Required when using testcase_name to specify which test run's test case you want. Example: 'test_run_6901b2abc6b187e63f536a6b'."New value: +"Single test run ID to filter results. Example: 'test_run_6901b2abc6b187e63f536a6b'."

addedInput schema / properties / testrun_ids

Added value: +{
+  "description": "Multiple test run IDs (comma-separated, max 20). Example: 'test_run_abc,test_run_def'.",
+  "type": "string"
+}

addedInput schema / properties / testsuite_id

Added value: +{
+  "description": "Filter by test suite ID.",
+  "type": "string"
+}

First observedJan 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals key behaviors: the two identification methods, the requirement to pair testcase_name with testrun_id due to duplicate names, the detailed return payload, and the effect of steps_filter='failed_only' in stripping passing steps. This is strong disclosure, though it omits potential rate limits or auth requirements, which are not critical for a read operation.

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?

The description is a tight paragraph that front-loads the purpose, then efficiently covers identification methods, return contents, the filter option, and a usage example. Every sentence adds necessary information without redundancy, making it concise and well-structured.

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?

Despite having 12 parameters and no output schema, the description provides a complete overview of the main workflows: how to identify a test case, what data to expect, and how to narrow results. It does not cover deprecated parameters or history settings, but those are fully documented in the schema. The description is sufficient for correct tool selection and invocation.

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 description coverage is 100%, so the baseline is 3. The description adds valuable semantics beyond the schema by explaining when testcase_id can be used alone versus when testcase_name must be combined with testrun_id, and by clarifying the effect of steps_filter. This helps the agent correctly assemble parameters, raising the score above baseline.

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?

The description clearly states the tool's purpose with a specific verb and resource: 'Get detailed information about a specific test case.' It lists the returned data types (error message, code snippet, logs, artifacts), which helps distinguish it from generic list tools. However, it does not explicitly differentiate itself from sibling tools like debug_testcase, so it misses the top score for sibling distinction.

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?

The description gives practical usage context: 'Use this to debug why a test failed or understand how it executed' and includes a concrete example. It does not mention alternatives or exclusions, but the context is sufficiently clear for an agent to know when this tool is appropriate.

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

get_testcase_details

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools