Testiny Test Management

Move a test case folder

moveFolder

Idempotent

Moves a test case folder to a different parent folder. Use targetParentId=0 to move it to root level. Rejects moves that would create a circular hierarchy. A move changes the folder's '_etag' and returns the new one - pass that to a later 'editFolder'.

Input Schema

Name	Required	Description
`project`	Yes	Project ID (number or string), project key or part of the project name
`folderId`	Yes	The id of the folder to move
`targetParentId`	Yes	The id of the target parent folder. Use 0 to move the folder to the root level.

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.
`status`	Yes
`folderId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false. The description adds genuinely new behavior beyond that: the circular-hierarchy validation rule and the fact that the move mutates '_etag' and returns the new value, which an agent needs for follow-up calls.

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?

Three tight sentences: purpose first, then the root special case, then the validation rule and return-value chaining. No filler, everything front-loaded.

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?

An output schema exists, so the description needn't explain return shape, yet it still flags the _etag change needed for chaining to editFolder. Only minor gaps remain (no mention of permission requirements or what happens to the moved folder's contents), which is acceptable for a simple move.

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 three parameters (project, folderId, targetParentId) are already documented in the schema, including the '0 = root' convention. The description repeats the root hint without adding syntax or format detail beyond the schema, so baseline 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?

States a specific verb and resource: 'Moves a test case folder to a different parent folder.' The resource ('test case folder') inherently distinguishes it from the sibling moveTestCases, but the description never explicitly names or contrasts that sibling, so it stops short of a 5.

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

Usage Guidelines3/5

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

It gives operational context (targetParentId=0 for root, circular moves rejected, chain the returned _etag into editFolder), but never states when to choose this tool over the near-identical moveTestCases sibling. Usage is implied rather than routed.

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?