Skip to main content
Glama

testmo_update_folder

Modify a Testmo folder's name, parent, documentation, or display order.

Instructions

Update a folder's name, parent, docs, or display order.

Args: project_id: The project ID. folder_id: The folder ID to update. name: New folder name (optional). parent_id: New parent folder ID (optional). docs: Docs text for the folder (optional). display_order: Display order in UI (optional).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
folder_idYes
nameNo
parent_idNo
docsNo
display_orderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the testmo_update_folder tool. It sends a PATCH request to the Testmo API to update a folder's name, parent_id, docs, or display_order.
    @mcp.tool()
    async def testmo_update_folder(
        project_id: int,
        folder_id: int,
        name: str | None = None,
        parent_id: int | None = None,
        docs: str | None = None,
        display_order: int | None = None,
    ) -> dict[str, Any]:
        """Update a folder's name, parent, docs, or display order.
    
        Args:
            project_id: The project ID.
            folder_id: The folder ID to update.
            name: New folder name (optional).
            parent_id: New parent folder ID (optional).
            docs: Docs text for the folder (optional).
            display_order: Display order in UI (optional).
        """
        data: dict[str, Any] = {"ids": [folder_id]}
        if name is not None:
            data["name"] = name
        if parent_id is not None:
            data["parent_id"] = parent_id
        if docs is not None:
            data["docs"] = docs
        if display_order is not None:
            data["display_order"] = display_order
        result = await _request("PATCH", f"/projects/{project_id}/folders", data=data)
        updated = result.get("result", [])
        return updated[0] if updated else result
  • The @mcp.tool() decorator registers the function as an MCP tool on the FastMCP server instance.
    @mcp.tool()
    async def testmo_update_folder(
  • Imports: mcp (FastMCP instance for tool registration), _request (HTTP client helper), and RATE_LIMIT_DELAY.
    from ..server import mcp
    from ..client import _request
    from ..config import RATE_LIMIT_DELAY
Behavior2/5

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

With no annotations, the description does not disclose behavioral traits beyond the basic fact that the tool mutates a folder. It lacks information on permissions, side effects, reversibility, or error conditions, leaving an agent with insufficient insight into the operation's implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (approximately 30 words plus a list) and front-loads the purpose. The parameter list uses a clear multi-line format, though it could be slightly more structured (e.g., using a table). No extraneous sentences.

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?

While the description covers the core purpose and parameters, it lacks usage guidelines, behavioral context, and any mention of return values. Despite having an output schema, the description does not reference it, leaving completeness moderate. It is adequate for a simple update tool but has clear gaps.

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?

Schema description coverage is 0%, so the description compensates by defining each parameter (project_id, folder_id, name, parent_id, docs, display_order) with a concise explanation and optionality. This adds meaning beyond the schema, which only provides types and titles.

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 clearly states the action ('update a folder') and lists the specific attributes that can be modified: name, parent, docs, display order. This distinguishes it from related tools like testmo_create_folder and testmo_delete_folder, though no explicit comparison is made.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use testmo_create_folder or testmo_delete_folder. There is no mention of prerequisites, context, or situations to avoid.

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