Skip to main content
Glama

testmo_create_folder

Create a new folder in a Testmo project to organize test cases. Specify a parent folder to create subfolders.

Instructions

Create a new folder in a Testmo project.

Args: project_id: The project ID. name: Folder name. parent_id: Parent folder ID (omit for root level).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
nameYes
parent_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual tool handler function for testmo_create_folder. Creates a folder via POST /projects/{project_id}/folders with name and optional parent_id.
    @mcp.tool()
    async def testmo_create_folder(
        project_id: int,
        name: str,
        parent_id: int | None = None,
    ) -> dict[str, Any]:
        """Create a new folder in a Testmo project.
    
        Args:
            project_id: The project ID.
            name: Folder name.
            parent_id: Parent folder ID (omit for root level).
        """
        folder_data: dict[str, Any] = {"name": name}
        if parent_id:
            folder_data["parent_id"] = parent_id
        result = await _request(
            "POST",
            f"/projects/{project_id}/folders",
            data={"folders": [folder_data]},
        )
        folders = result.get("result", [])
        return folders[0] if folders else result
  • The @mcp.tool() decorator registers testmo_create_folder as an MCP tool on the FastMCP server instance.
    @mcp.tool()
    async def testmo_create_folder(
  • The _request helper function used by the handler to call the Testmo REST API.
        )
    
    
    async def _request(
  • Type hints define the input schema: project_id (int), name (str), parent_id (int | None).
        project_id: int,
        name: str,
        parent_id: int | None = None,
    ) -> dict[str, Any]:
        """Create a new folder in a Testmo project.
    
        Args:
            project_id: The project ID.
            name: Folder name.
            parent_id: Parent folder ID (omit for root level).
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action (create) but does not disclose behavioral traits such as required permissions, side effects on other resources, or error conditions.

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 extremely concise (5 lines) and well-structured with an 'Args:' section. Every sentence provides direct value, no redundancy or fluff.

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?

Given no annotations and a moderately complex creation tool, the description covers purpose and parameter meanings adequately. However, it omits return value behavior (output schema exists but unknown content) and fails to address error handling or permissions.

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

Parameters4/5

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

With 0% schema description coverage, the description adds value by explaining each parameter: project_id as project ID, name as folder name, parent_id as parent folder ID with hint to omit for root level. This clarifies beyond schema titles.

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 'Create a new folder in a Testmo project', identifying the verb and resource. It distinguishes from sibling tools like testmo_update_folder and testmo_delete_folder by specifying creation specifically.

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?

The description implies usage by outlining parameters, but lacks explicit guidance on when to use this tool versus alternatives (e.g., update_folder). It does not mention prerequisites or context like project existence.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/strelec00/testmo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server