Skip to main content
Glama

testmo_list_runs

Retrieve test runs for a project with optional filters by closed status, milestone, and pagination controls.

Instructions

List test runs in a project.

Args: project_id: The project ID. page: Page number (default: 1). per_page: Results per page (default: 100). Valid: 25, 50, 100. is_closed: Filter by closed status. milestone_id: Comma-separated milestone IDs to filter by. expands: Related entities to include.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
pageNo
per_pageNo
is_closedNo
milestone_idNo
expandsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for testmo_list_runs. Uses the @mcp.tool() decorator to register as an MCP tool. Accepts project_id, page, per_page, is_closed, milestone_id, and expands parameters, then calls the Testmo API GET /projects/{project_id}/runs endpoint.
    @mcp.tool()
    async def testmo_list_runs(
        project_id: int,
        page: int = 1,
        per_page: int = 100,
        is_closed: bool | None = None,
        milestone_id: str | None = None,
        expands: list[str] | None = None,
    ) -> dict[str, Any]:
        """List test runs in a project.
    
        Args:
            project_id: The project ID.
            page: Page number (default: 1).
            per_page: Results per page (default: 100). Valid: 25, 50, 100.
            is_closed: Filter by closed status.
            milestone_id: Comma-separated milestone IDs to filter by.
            expands: Related entities to include.
        """
        params: dict[str, Any] = {"page": page, "per_page": per_page}
        if is_closed is not None:
            params["is_closed"] = is_closed
        if milestone_id:
            params["milestone_id"] = milestone_id
        if expands:
            params["expands"] = ",".join(expands)
        return await _request("GET", f"/projects/{project_id}/runs", params=params)
  • testmo-mcp.py:15-15 (registration)
    Registration of the runs module (which includes testmo_list_runs) via import of testmo.tools.runs module in the main entry point.
    import testmo.tools.runs  # noqa: F401
  • The _request helper function used by testmo_list_runs to make HTTP requests to the Testmo API.
    async def _request(
        method: str,
        endpoint: str,
        data: dict[str, Any] | None = None,
        params: dict[str, Any] | None = None,
    ) -> dict[str, Any]:
        async with _get_client() as client:
            response = await client.request(
                method=method,
                url=endpoint,
                json=data,
                params=params,
            )
            if response.status_code == 204:
                return {"success": True}
            if response.status_code >= 400:
                try:
                    error_body = response.json()
                except Exception:
                    error_body = response.text
                raise RuntimeError(
                    f"Testmo API error {response.status_code}: "
                    f"{json.dumps(error_body) if isinstance(error_body, dict) else error_body}"
                )
            return response.json()
  • The FastMCP server instance (mcp) that provides the @mcp.tool() decorator used to register testmo_list_runs.
    mcp = FastMCP("testmo-mcp")
Behavior3/5

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

Annotations are missing, so the description carries the full burden. It mentions pagination and filtering, which implies a read-only operation, but does not disclose rate limits, data volumes, or potential side effects. The existence of an output schema partially compensates for missing return details.

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 very concise: a single-line purpose followed by a clean args list. No redundant information. It is front-loaded and to the point.

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 covers the purpose and parameters adequately, but it lacks details on what 'expands' includes (which related entities), sorting or ordering, and any default limits. The output schema may cover return format, but some context is missing for a fully informed selection.

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 adds significant value by explaining defaults (page=1, per_page=100), valid values for per_page (25,50,100), and that mile stone_id is comma-separated. This goes beyond the raw schema.

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 'List test runs in a project' with a specific verb and resource. It distinguishes well from siblings like testmo_get_run (single run) and testmo_list_run_results (results for a run).

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 testmo_list_automation_runs or testmo_get_run. There is no mention of prerequisites, context, or exclusions.

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