TestDino MCP

create_manual_test_case

Create a new manual test case to document test scenarios, including steps, preconditions, postconditions, and metadata such as priority and severity.

Instructions

Create a new manual test case. Use this to document new test scenarios, features, or requirements. Supports adding test steps, preconditions, postconditions, and metadata like priority, severity, and type.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Tags to add to your test cases.
`type`	No	Test case type.
`flags`	No	Automation flags/checklist options.
`layer`	No	Test layer.
`steps`	No	Array of test steps. For Classic format: action, expectedResult, and optional data. For Gherkin format: event and stepDescription. Each top-level step can include attachments as URLs or local file paths.
`title`	Yes	Test case title (Required). A clear, descriptive title for the test case.
`status`	No	Test case status.
`behavior`	No	Test behavior type.
`priority`	No	Test case priority level.
`severity`	No	Test case severity level.
`projectId`	Yes	Project ID (Required). The TestDino project identifier.
`suiteName`	Yes	Test suite name (Required). The suite where this test case will be created. Use list_manual_test_suites to find suite names.
`attachments`	No	Array of attachment URLs or file paths (up to 10MB each).
`description`	No	Detailed description of what this test case validates.
`customFields`	No	Custom fields as key-value pairs. Only available if custom fields are configured in test case management settings.
`preconditions`	No	Prerequisites or setup required before executing this test case.
`postconditions`	No	Expected state or cleanup actions after executing this test case.
`automationStatus`	No	Automation status of the test case.
`testStepsDeclarationType`	No	Type of test steps declaration format.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv1.0.10May 19, 2026

addedInput schema / properties / attachments

Added value: +{
+  "description": "Array of attachment URLs or file paths (up to 10MB each).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / automationStatus

Added value: +{
+  "description": "Automation status of the test case.",
+  "enum": [
+    "Manual",
+    "Automated",
+    "To be automated"
+  ],
+  "type": "string"
+}

changedInput schema / properties / behavior / enum

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

addedInput schema / properties / customFields

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Custom fields as key-value pairs. Only available if custom fields are configured in test case management settings.",
+  "type": "object"
+}

addedInput schema / properties / flags

Added value: +{
+  "description": "Automation flags/checklist options.",
+  "items": {
+    "enum": [
+      "To be Automated",
+      "Is flaky",
+      "Muted"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / layer / enum

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

changedInput schema / properties / priority / enum

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

changedInput schema / properties / severity / enum

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

addedInput schema / properties / status

Added value: +{
+  "description": "Test case status.",
+  "enum": [
+    "Active",
+    "Draft",
+    "Deprecated"
+  ],
+  "type": "string"
+}

changedInput schema / properties / steps / description

Previous value: -"Array of test steps. Each step should have action, expectedResult, and optional data fields."New value: +"Array of test steps. For Classic format: action, expectedResult, and optional data. For Gherkin format: event and stepDescription. Each top-level step can include attachments as URLs or local file paths."

addedInput schema / properties / steps / items / oneOf

Added value: +[
+  {
+    "properties": {
+      "action": {
+        "description": "The action to perform in this step (Classic format).",
+        "type": "string"
+      },
+      "attachments": {
+        "description": "Optional top-level step attachments as URLs or local file paths.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "data": {
+        "description": "Optional test data for this step (Classic format).",
+        "type": "string"
+      },
+      "expectedResult": {
+        "description": "The expected outcome of this action (Classic format).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "action",
+      "expectedResult"
+    ]
+  },
+  {
+    "properties": {
+      "attachments": {
+        "description": "Optional top-level step attachments as URLs or local file paths.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "event": {
+        "description": "Gherkin event keyword (Gherkin format).",
+        "enum": [
+          "Given",
+          "When",
+          "And",
+          "Then",
+          "But"
+        ],
+        "type": "string"
+      },
+      "stepDescription": {
+        "description": "The step description (Gherkin format).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "event",
+      "stepDescription"
+    ]
+  }
+]

removedInput schema / properties / steps / items / properties

Removed value: -{
-  "action": {
-    "description": "The action to perform in this step.",
-    "type": "string"
-  },
-  "data": {
-    "description": "Optional test data for this step.",
-    "type": "string"
-  },
-  "expectedResult": {
-    "description": "The expected outcome of this action.",
-    "type": "string"
-  }
-}

removedInput schema / properties / steps / items / required
```
Removed value: -[
-  "action",
-  "expectedResult"
-]
```

removedInput schema / properties / suiteId

Removed value: -{
-  "description": "Test suite ID (Required). The suite where this test case will be created. Use list_manual_test_suites to find suite IDs.",
-  "type": "string"
-}

addedInput schema / properties / suiteName

Added value: +{
+  "description": "Test suite name (Required). The suite where this test case will be created. Use list_manual_test_suites to find suite names.",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Tags to add to your test cases.",
+  "type": "string"
+}

addedInput schema / properties / testStepsDeclarationType

Added value: +{
+  "description": "Type of test steps declaration format.",
+  "enum": [
+    "Classic",
+    "Gherkin"
+  ],
+  "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"
+]

changedInput schema / required

Previous value: -[
-  "projectId",
-  "title",
-  "suiteId"
-]New value: +[
+  "projectId",
+  "title",
+  "suiteName"
+]

First observedJan 29, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It states the tool creates a test case, but does not mention any side effects, required permissions, rate limits, or error handling. For a creation tool, this minimal transparency is inadequate.

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 two sentences, front-loading the core purpose. Every sentence adds value, and there is no redundancy or wasted text.

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?

The tool has 19 parameters and no output schema. The description lacks information about what the tool returns upon success (e.g., ID of created test case) or potential errors. Given the complexity, the description is incomplete.

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?

The input schema has 100% coverage with detailed parameter descriptions. The description adds marginal value by summarizing supported fields ('test steps, preconditions, postconditions, and metadata'), but does not provide additional meaning beyond what the schema already conveys. Baseline 3 is appropriate.

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 states the tool's action ('Create a new manual test case') and resource ('manual test case'). It distinguishes from sibling tools like create_manual_run or create_manual_test_suite by specifying it's for documenting test scenarios, features, or requirements.

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 explicitly says 'Use this to document new test scenarios, features, or requirements,' which provides clear usage context. However, it does not mention when not to use it or suggest alternatives (e.g., use create_manual_run for executing test cases), so it stops short of a 5.

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

create_manual_test_case

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools