Skip to main content
Glama
henihaddad

GCP MCP

by henihaddad
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_cloud_build_triggers

List Cloud Build triggers in a specified GCP project to manage and monitor automated build configurations efficiently.

Instructions

    List Cloud Build triggers in a GCP project.
    
    Args:
        project_id: The ID of the GCP project to list build triggers for
    
    Returns:
        List of Cloud Build triggers in the specified GCP project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • src/gcp_mcp/gcp_modules/deployment/tools.py:38-50 (handler)
    The handler function implementing the 'list_cloud_build_triggers' tool logic (currently a TODO placeholder with input validation via type hints and docstring serving as schema). The @mcp.tool() decorator also handles registration.
    @mcp.tool()
def list_cloud_build_triggers(project_id: str) -> str:
    """
    List Cloud Build triggers in a GCP project.
    
    Args:
        project_id: The ID of the GCP project to list build triggers for
    
    Returns:
        List of Cloud Build triggers in the specified GCP project
    """
    # TODO: Implement this function
    return f"Not yet implemented: listing Cloud Build triggers for project {project_id}"
  • src/gcp_mcp/server.py:60-60 (registration)
    Top-level registration call for the deployment tools module, which registers the 'list_cloud_build_triggers' tool.
    deployment_tools.register_tools(mcp)
  • src/gcp_mcp/server.py:15-15 (registration)
    Import of the deployment tools module containing the 'list_cloud_build_triggers' implementation and registration.
    from .gcp_modules.deployment import tools as deployment_tools
  • src/gcp_mcp/gcp_modules/deployment/tools.py:6-7 (registration)
    The module-level register_tools function that defines and registers multiple tools, including 'list_cloud_build_triggers' via nested @mcp.tool() decorators.
    def register_tools(mcp):
    """Register all deployment tools with the MCP server."""

Tool Definition Quality

C2.9/5.0
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 mentions listing triggers but fails to disclose behavioral traits like pagination, rate limits, permission requirements, or output format details. This is a significant gap for a tool with no annotation coverage.

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 front-loaded with the purpose, followed by structured Args and Returns sections. It is appropriately sized with no redundant sentences, though the formatting could be slightly more streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on authentication, error handling, return structure, and behavioral constraints, making it inadequate for a tool that interacts with GCP resources.

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 0%, but the description adds meaning by explaining that 'project_id' is for specifying the GCP project to list build triggers for. This compensates partially, though it doesn't detail format constraints or examples. With one parameter, the baseline is 4, but the lack of schema coverage reduces it to 3.

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 verb ('List') and resource ('Cloud Build triggers in a GCP project'), making the purpose unambiguous. However, it does not differentiate from sibling tools like 'list_cloud_sql_instances' or 'list_gke_clusters' beyond the specific resource type, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It lacks context about prerequisites (e.g., authentication), exclusions, or comparisons to other list tools, leaving the agent to infer usage based on the resource name alone.

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

Related 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/henihaddad/gcp-mcp'

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