TestRail MCP Server

mutate_section

Create new sections or update existing ones in TestRail by providing the action type and section attributes.

Instructions

Create a new section or update an existing section in TestRail. Set payload.action to 'create' or 'update' to specify the operation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payload`	Yes	The mutation payload containing the action (create or update) and the corresponding section attributes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Sep 22, 2026

changedInput schema / properties / payload / oneOf

Previous value: -[
-  {
-    "properties": {
-      "action": {
-        "const": "create",
-        "description": "The operation to perform: create a new section",
-        "type": "string"
-      },
-      "description": {
-        "description": "The description of the section",
-        "type": "string"
-      },
-      "name": {
-        "description": "The name of the section",
-        "type": "string"
-      },
-      "parent_id": {
-        "description": "The ID of the parent section (to build section hierarchies)",
-        "type": "number"
-      },
-      "project_id": {
-        "description": "The ID of the project the section should be added to",
-        "type": "number"
-      },
-      "suite_id": {
-        "description": "The ID of the test suite (required for multi-suite projects, i.e. suite_mode=2 or 3). Use get_suites to find available suites",
-        "type": "number"
-      }
-    },
-    "required": [
-      "name",
-      "action",
-      "project_id"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "action": {
-        "const": "update",
-        "description": "The operation to perform: update an existing section",
-        "type": "string"
-      },
-      "description": {
-        "description": "The description of the section",
-        "type": "string"
-      },
-      "name": {
-        "description": "The name of the section",
-        "type": "string"
-      },
-      "section_id": {
-        "description": "The ID of the section to update",
-        "type": "number"
-      }
-    },
-    "required": [
-      "action",
-      "section_id"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "action": {
+        "const": "create",
+        "description": "The operation to perform: create a new section",
+        "type": "string"
+      },
+      "description": {
+        "description": "The description of the section",
+        "type": "string"
+      },
+      "name": {
+        "description": "The name of the section",
+        "type": "string"
+      },
+      "parent_id": {
+        "description": "The ID of the parent section (to build section hierarchies)",
+        "type": "number"
+      },
+      "project_id": {
+        "description": "The ID of the project the section should be added to",
+        "type": "number"
+      },
+      "suite_id": {
+        "description": "The ID of the test suite (required for multi-suite projects, i.e. suite_mode=2 or 3). Use query_suite to find available suites",
+        "type": "number"
+      }
+    },
+    "required": [
+      "name",
+      "action",
+      "project_id"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "action": {
+        "const": "update",
+        "description": "The operation to perform: update an existing section",
+        "type": "string"
+      },
+      "description": {
+        "description": "The description of the section",
+        "type": "string"
+      },
+      "name": {
+        "description": "The name of the section",
+        "type": "string"
+      },
+      "section_id": {
+        "description": "The ID of the section to update",
+        "type": "number"
+      }
+    },
+    "required": [
+      "action",
+      "section_id"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedv2.2.0Jul 31, 2026

changedInput schema / properties / payload / oneOf

Previous value: -[
-  {
-    "properties": {
-      "action": {
-        "const": "create",
-        "description": "The operation to perform: create a new section",
-        "type": "string"
-      },
-      "description": {
-        "description": "The description of the section",
-        "type": "string"
-      },
-      "name": {
-        "description": "The name of the section",
-        "type": "string"
-      },
-      "parent_id": {
-        "description": "The ID of the parent section (to build section hierarchies)",
-        "type": "number"
-      },
-      "project_id": {
-        "description": "The ID of the project the section should be added to",
-        "type": "number"
-      }
-    },
-    "required": [
-      "name",
-      "action",
-      "project_id"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "action": {
-        "const": "update",
-        "description": "The operation to perform: update an existing section",
-        "type": "string"
-      },
-      "description": {
-        "description": "The description of the section",
-        "type": "string"
-      },
-      "name": {
-        "description": "The name of the section",
-        "type": "string"
-      },
-      "section_id": {
-        "description": "The ID of the section to update",
-        "type": "number"
-      }
-    },
-    "required": [
-      "action",
-      "section_id"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "action": {
+        "const": "create",
+        "description": "The operation to perform: create a new section",
+        "type": "string"
+      },
+      "description": {
+        "description": "The description of the section",
+        "type": "string"
+      },
+      "name": {
+        "description": "The name of the section",
+        "type": "string"
+      },
+      "parent_id": {
+        "description": "The ID of the parent section (to build section hierarchies)",
+        "type": "number"
+      },
+      "project_id": {
+        "description": "The ID of the project the section should be added to",
+        "type": "number"
+      },
+      "suite_id": {
+        "description": "The ID of the test suite (required for multi-suite projects, i.e. suite_mode=2 or 3). Use get_suites to find available suites",
+        "type": "number"
+      }
+    },
+    "required": [
+      "name",
+      "action",
+      "project_id"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "action": {
+        "const": "update",
+        "description": "The operation to perform: update an existing section",
+        "type": "string"
+      },
+      "description": {
+        "description": "The description of the section",
+        "type": "string"
+      },
+      "name": {
+        "description": "The name of the section",
+        "type": "string"
+      },
+      "section_id": {
+        "description": "The ID of the section to update",
+        "type": "number"
+      }
+    },
+    "required": [
+      "action",
+      "section_id"
+    ],
+    "type": "object"
+  }
+]

Addedv2.0.0Jun 3, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The annotations already flag readOnly=false, idempotent=false, and destructive=false, and the description does not add meaningful behavioral context beyond 'create or update.' It does not disclose postconditions, overwrite behavior, or what happens on the update branch, so the agent is left without additional operational expectations.

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 one clear sentence plus a short actionable instruction. It is front-loaded with the verb and resource and contains no filler.

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

Completeness3/5

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

The description and schema together are sufficient to know what action to set and which fields are required for each branch. However, there is no output schema and the description does not mention return behavior, success/failure signals, or prerequisites like resolving suite_id with query_suite (which only appears in the schema).

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 description coverage is 100%, so the schema already explains every parameter. The only additional instruction, 'Set payload.action to create or update,' restates what the schema's action const/descriptions already convey; it does not add new semantics.

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 names a specific operation and resource: create or update a TestRail section. It clearly communicates the dual-action nature but does not distinguish this from sibling mutation tools like mutate_suite beyond the resource name.

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

Usage Guidelines2/5

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

The description only explains how to choose between the two internal operations ('create' vs 'update') via payload.action. It gives no guidance about when to select this tool over sibling tools such as query_section for reads or mutate_suite for suite-level mutations.

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

mutate_section

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools