Skip to main content
Glama

testmo_list_automation_sources

List CI/CD integration sources for a Testmo project, with optional filtering by retired status, pagination, and related entity expansion.

Instructions

List automation sources in a project (CI/CD integrations).

Args: project_id: The project ID. is_retired: Filter by retired status (optional). page: Page number (default: 1). per_page: Results per page (default: 100). Valid: 25, 50, 100. expands: Related entities to include.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
is_retiredNo
pageNo
per_pageNo
expandsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'testmo_list_automation_sources' tool. It is decorated with @mcp.tool() and makes a GET request to /projects/{project_id}/automation/sources with optional query parameters (is_retired, page, per_page, expands).
    @mcp.tool()
    async def testmo_list_automation_sources(
        project_id: int,
        is_retired: bool | None = None,
        page: int = 1,
        per_page: int = 100,
        expands: list[str] | None = None,
    ) -> dict[str, Any]:
        """List automation sources in a project (CI/CD integrations).
    
        Args:
            project_id: The project ID.
            is_retired: Filter by retired status (optional).
            page: Page number (default: 1).
            per_page: Results per page (default: 100). Valid: 25, 50, 100.
            expands: Related entities to include.
        """
        params: dict[str, Any] = {"page": page, "per_page": per_page}
        if is_retired is not None:
            params["is_retired"] = is_retired
        if expands:
            params["expands"] = ",".join(expands)
        return await _request(
            "GET", f"/projects/{project_id}/automation/sources", params=params
        )
  • Registration of the tool via the @mcp.tool() decorator, which registers 'testmo_list_automation_sources' with the FastMCP server.
    @mcp.tool()
  • The _request helper function used by the handler to execute the HTTP request against 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') used as the decorator target for registering all tools.
    mcp = FastMCP("testmo-mcp")
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'List', implying read-only, but doesn't mention pagination behavior, permissions, rate limits, or side effects. The pagination parameters are listed but their impact on results is not described.

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 concise, using a list format for parameters. Every sentence adds useful information without redundancy, and the purpose is stated upfront.

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 the tool has 5 parameters and an output schema, the description covers parameter basics but lacks behavioral context (e.g., how pagination works, error handling). The output schema exists so return values are covered, but the description doesn't mention the overall response structure.

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?

With 0% schema description coverage, the description adds partial value: it clarifies 'is_retired' as a filter, notes valid values for 'per_page' (25,50,100), and explains 'expands' as related entities. However, 'expands' possibilities are not listed, and other parameters merely repeat schema defaults.

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 automation sources in a project (CI/CD integrations)', specifying the action and resource. It distinguishes from sibling tools like 'get_automation_source' (single retrieval) and other list/list operations.

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 when to use (when needing to list automation sources) but lacks explicit guidance on when not to use or alternatives. No comparison with sibling tools is provided.

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