Skip to main content
Glama

list_webhooks

Retrieve all webhooks configured for a specific Codemagic application by providing its application ID.

Instructions

List all webhooks configured for a Codemagic application.

Args: app_id: The Codemagic application ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes

Implementation Reference

  • The MCP tool handler for list_webhooks. It accepts an app_id string and calls the client's list_webhooks method.
    async def list_webhooks(app_id: str) -> Any:
        """List all webhooks configured for a Codemagic application.
    
        Args:
            app_id: The Codemagic application ID.
        """
        async with CodemagicClient() as client:
            return await client.list_webhooks(app_id)
  • The underlying HTTP client method that performs a GET request to /apps/{app_id}/webhooks.
    async def list_webhooks(self, app_id: str) -> Any:
        return await self._get(f"/apps/{app_id}/webhooks")
  • The register function that decorates and registers list_webhooks as an MCP tool via @mcp.tool().
    def register(mcp: FastMCP) -> None:
        @mcp.tool()
        async def list_webhooks(app_id: str) -> Any:
            """List all webhooks configured for a Codemagic application.
    
            Args:
                app_id: The Codemagic application ID.
            """
            async with CodemagicClient() as client:
                return await client.list_webhooks(app_id)
  • Top-level registration orchestrator that calls webhooks.register(mcp) along with other tool modules.
    def register_all_tools(mcp: FastMCP) -> None:
        apps.register(mcp)
        builds.register(mcp)
        artifacts.register(mcp)
        caches.register(mcp)
        variables.register(mcp)
        webhooks.register(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 beyond the basic operation. It only states 'list all webhooks' without mentioning read-only nature, side effects, or permissions. Minimal behavioral context.

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 short with two sentences and a parameter list. No wasted words; essential information is front-loaded.

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?

For a list operation, the description lacks information about the return value structure, pagination, or limits. With no output schema, this gap leaves the agent uninformed about what the response contains.

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?

The description adds meaning to the parameter by stating it is 'The Codemagic application ID,' which goes beyond the schema's title 'App Id'. Schema coverage is 0%, so description compensates well.

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 the action ('list'), the resource ('webhooks'), and the scope ('for a Codemagic application'), distinguishing it from sibling tools like add_webhook and delete_webhook.

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. Sibling tools exist (add_webhook, delete_webhook) but no when-to-use or when-not-to-use information is given.

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/AgiMaulana/CodemagicMcp'

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