Skip to main content
Glama

list_webhooks

Retrieve all configured webhooks for a Codemagic application to monitor integration points and manage event notifications.

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 tool handler for 'list_webhooks', registered with FastMCP.
    @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)
  • Registration function that exposes 'list_webhooks' as an MCP tool.
    def register(mcp: FastMCP) -> None:
Behavior2/5

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

No annotations provided, yet description fails to disclose read-only status, pagination behavior, return format, or error conditions (e.g., invalid app_id). Only states functional purpose without operational characteristics.

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?

Main sentence is concise and front-loaded. Args section efficiently documents the single parameter. Docstring-style 'Args:' formatting is clear but slightly informal for MCP standards.

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?

Adequate for a single-parameter list operation: covers purpose and parameter identity. However, lacks return value description and behavioral context expected given no output schema exists.

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 has 0% description coverage (only title 'App Id'). The Args section explicitly documents 'app_id: The Codemagic application ID', adding critical semantic meaning absent from the structured 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?

Specifies exact action 'List' with resource 'webhooks' and scope 'for a Codemagic application'. The verb clearly distinguishes from sibling tools 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no explicit when-to-use guidance or prerequisites beyond the app_id requirement. Usage is implied by the 'List' verb but lacks context about when to prefer this over direct webhook management or caching considerations.

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