TestDino MCP

update_manual_test_case

Update existing manual test case fields: steps, status, priority, comments, Jira links, and more. Send only the fields to change.

Instructions

Update an existing manual test case. Use this to modify test case details, steps, status, priority, or any other fields. Provide only the fields you want to update in the updates object. To add comments, pass updates.comments as an array of strings — each becomes a new comment (PAT owner is author). To link Jira issues, pass updates.issues as an array of ticket keys (e.g. ['PROJ-123']); the server looks each up in the project's connected Jira and saves with title+url, or as a plain text stub when Jira isn't connected or the ticket isn't found (same fallback as the UI). Automated-test links are NOT writable here — updates.linkedTests is rejected; use link_automated_test / bulk_link_automated_tests / unlink_automated_test.

Input Schema

TableJSON Schema

Name	Required	Description
`caseId`	Yes	Test case ID (Required). Can be internal _id or human-readable ID like 'TC-123'.
`updates`	Yes	Object containing the fields to update. Can include: title (or name), description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions, automationStatus, tags, flags, attachments, customFields, etc.
`projectId`	Yes	Project ID (Required). The TestDino project identifier.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.2Aug 12, 2026

changedInput schema / properties / updates / description

Previous value: -"Object containing the fields to update. Can include: name, description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions, automationStatus, tags, flags, attachments, customFields, etc."New value: +"Object containing the fields to update. Can include: title (or name), description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions, automationStatus, tags, flags, attachments, customFields, etc."

changedInput schema / properties / updates / properties / name / description

Previous value: -"Updated test case name/title."New value: +"Updated test case title (or name). `title` is the rename-safe primary field; `name` is accepted as an alias."

Changed20 schema fields changedv1.0.10May 19, 2026

changedInput schema / properties / updates / description

Previous value: -"Object containing the fields to update. Can include: title, description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions, etc."New value: +"Object containing the fields to update. Can include: name, description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions, automationStatus, tags, flags, attachments, customFields, etc."

addedInput schema / properties / updates / properties / attachments

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

addedInput schema / properties / updates / properties / automationStatus

Added value: +{
+  "description": "Updated automation status.",
+  "enum": [
+    "Manual",
+    "Automated",
+    "To be automated"
+  ],
+  "type": "string"
+}

changedInput schema / properties / updates / properties / behavior / enum

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

addedInput schema / properties / updates / properties / comments

Added value: +{
+  "description": "Array of comment bodies to append to the test case. Each string becomes a new comment with the PAT owner as the author. The server enforces a cap of 20 comments per case; entries past the cap are rejected.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / updates / properties / customFields

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

addedInput schema / properties / updates / properties / flags

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

addedInput schema / properties / updates / properties / issues

Added value: +{
+  "description": "Array of Jira ticket keys to link to the test case (e.g. ['PROJ-123', 'ENG-45']). The server resolves each key against the project's connected Jira: tickets that are found are saved with title and URL; tickets that aren't found (or if no Jira is connected) are saved as plain text stubs — same fallback as the UI's add-issue flow. Duplicate links for the same ticket are silently skipped.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / updates / properties / layer / enum

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

addedInput schema / properties / updates / properties / name

Added value: +{
+  "description": "Updated test case name/title.",
+  "type": "string"
+}

changedInput schema / properties / updates / properties / priority / enum

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

changedInput schema / properties / updates / properties / severity / enum

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

changedInput schema / properties / updates / properties / status / enum

Previous value: -[
-  "actual",
-  "draft",
-  "deprecated"
-]New value: +[
+  "Active",
+  "Draft",
+  "Deprecated"
+]

changedInput schema / properties / updates / properties / steps / description

Previous value: -"Updated test steps array."New value: +"Updated test steps array. 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 / updates / 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": {
+        "enum": [
+          "Given",
+          "When",
+          "And",
+          "Then",
+          "But"
+        ],
+        "type": "string"
+      },
+      "stepDescription": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "event",
+      "stepDescription"
+    ]
+  }
+]

removedInput schema / properties / updates / properties / steps / items / properties

Removed value: -{
-  "action": {
-    "type": "string"
-  },
-  "data": {
-    "type": "string"
-  },
-  "expectedResult": {
-    "type": "string"
-  }
-}

addedInput schema / properties / updates / properties / tags

Added value: +{
+  "description": "Updated tags.",
+  "type": "string"
+}

addedInput schema / properties / updates / properties / testStepsDeclarationType

Added value: +{
+  "description": "Updated test steps declaration type.",
+  "enum": [
+    "Classic",
+    "Gherkin"
+  ],
+  "type": "string"
+}

removedInput schema / properties / updates / properties / title

Removed value: -{
-  "description": "Updated test case title.",
-  "type": "string"
-}

changedInput schema / properties / updates / 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

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries full behavioral burden and succeeds: it discloses that comments are appended with the PAT owner as author, that a 20-comment cap exists, that Jira issue links fall back to plain-text stubs when unresolved, that duplicate issue links are silently skipped, and that linkedTests is rejected.

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 dense but every sentence earns its place. It front-loads the core purpose, then covers partial updates, special fields, fallback behavior, and exclusions in a logical order. No filler or repetition of schema-only details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex nested-object update tool with no annotations and no output schema, the description is remarkably complete. It covers the key invocation semantics, special-field behaviors, failure/exclusion cases, and sibling alternatives, leaving an agent well-equipped to call it correctly.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds important semantic context beyond the schema: partial-update behavior ('Provide only the fields you want to update'), comment authorship and cap, Jira resolution/fallback behavior, and the explicit rejection of linkedTests. These details materially change how an agent should construct the updates object.

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 opens with a specific verb+resource: 'Update an existing manual test case.' It then enumerates the updatable fields (details, steps, status, priority, or any other fields), making the tool's scope unmistakable and distinguishing it from create/run/suite operations among the siblings.

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

Usage Guidelines5/5

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

It explicitly says 'Use this to modify test case details...' and provides a clear when-not case: automated-test links are NOT writable here, with named alternatives (link_automated_test, bulk_link_automated_tests, unlink_automated_test). This is direct, actionable routing guidance.

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

update_manual_test_case

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools