Testiny Test Management

Create a new test case folder

createFolder

Creates a new test case folder in a project, optionally nested under an existing folder.

Input Schema

Name	Required	Description
`title`	Yes	The title of the new folder
`format`	No	Format for rich-text fields (descriptions, preconditions, comments, step & result cells, stepsText & expectedResultText) on both input and output: 'markdown' (default) or 'xml'. Read the matching rich-text format reference resource before producing either. Use 'xml' for BOTH the read and the write whenever you are changing a field that already has content: markdown cannot carry an underline or a text color, so an edit written as markdown writes those away. 'markdown' is for writing new content and for reading you will not edit.
`project`	Yes	Project ID (number or string), project key or part of the project name
`description`	No	An optional description for the folder - rich text in the chosen 'format'
`parentFolder`	No	Optional parent folder: title substring, numeric id, or ID-format like TCF-123. Omit or leave empty to create at root level - use 'moveFolder' with targetParentId=0 to move it back to the root later.

Output Schema

Name	Required	Description
`_etag`	No	Conflict tag of the entity - pass it to an edit tool's '_etag' to have that edit rejected if somebody changed the entity in the meantime. Empty for an entity that carries no tag yet.
`title`	No
`status`	Yes
`folderId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 12, 2026

changedInput schema / properties / description / description

Previous value: -"An optional description for the folder - can include simple markdown"New value: +"An optional description for the folder - rich text in the chosen 'format'"

addedInput schema / properties / format

Added value: +{
+  "description": "Format for rich-text fields (descriptions, preconditions, comments, step & result cells, stepsText & expectedResultText) on both input and output: 'markdown' (default) or 'xml'. Read the matching rich-text format reference resource before producing either. Use 'xml' for BOTH the read and the write whenever you are changing a field that already has content: markdown cannot carry an underline or a text color, so an edit written as markdown writes those away. 'markdown' is for writing new content and for reading you will not edit.",
+  "enum": [
+    "markdown",
+    "xml"
+  ],
+  "type": "string"
+}

changedInput schema / properties / parentFolder / description

Previous value: -"Optional parent folder: title substring, numeric id, or ID-format like TCF-123. Omit or leave empty to create at root level."New value: +"Optional parent folder: title substring, numeric id, or ID-format like TCF-123. Omit or leave empty to create at root level - use 'moveFolder' with targetParentId=0 to move it back to the root later."

addedOutput schema / properties / _etag

Added value: +{
+  "description": "Conflict tag of the entity - pass it to an edit tool's '_etag' to have that edit rejected if somebody changed the entity in the meantime. Empty for an entity that carries no tag yet.",
+  "type": "string"
+}

First observedOct 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds the nesting behavior, but does not disclose anything an agent couldn't infer from the annotations and schema, such as whether duplicate folder titles are allowed or what permissions are required.

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?

A single sentence that front-loads the action and resource and includes the one scoping nuance (optional nesting) without padding. Every clause earns its place.

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?

With an output schema present, return values need not be explained, and the 100%-covered schema plus annotations cover inputs and safety. The definition is nearly complete for a simple create tool; only the absence of usage/duplicate-handling guidance keeps it from a 5.

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 all five parameters are already documented in the schema, including the parentFolder root-level behavior and the format semantics. The description adds no parameter detail beyond restating that nesting is optional, so the baseline of 3 applies.

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 gives a specific verb+resource ('Creates a new test case folder') plus its scope ('in a project, optionally nested'), which clearly separates it from sibling tools like createTestCase or createTestRun. It stops short of naming a sibling alternative, but the resource is unambiguous.

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?

There is no when-to-use or when-not guidance. The description never tells the agent when to create a folder versus using createTestCase directly, nor does it reference editFolder/moveFolder as follow-ups (that hint only appears in the parentFolder schema description, not the tool description).

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

All Testiny Test Management tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?