Skip to main content
Glama
AgiMaulana

Codemagic

by AgiMaulana
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_webhook

Destructive

Remove a webhook from a Codemagic CI/CD application to stop receiving automated notifications or triggers from that integration.

Instructions

Delete a webhook from a Codemagic application.

Args: app_id: The Codemagic application ID. webhook_id: The webhook ID to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes
webhook_idYes

Implementation Reference

  • codemagic_mcp/tools/webhooks.py:32-41 (handler)
    The tool handler for 'delete_webhook' which calls the Codemagic client.
    @mcp.tool(annotations=ToolAnnotations(destructiveHint=True))
async def delete_webhook(app_id: str, webhook_id: str) -> Any:
    """Delete a webhook from a Codemagic application.

    Args:
        app_id: The Codemagic application ID.
        webhook_id: The webhook ID to delete.
    """
    async with CodemagicClient() as client:
        return await client.delete_webhook(app_id, webhook_id)
  • codemagic_mcp/client.py:329-330 (handler)
    The API client method that performs the actual HTTP DELETE request to remove a webhook.
    async def delete_webhook(self, app_id: str, webhook_id: str) -> Any:
    return await self._delete(f"/apps/{app_id}/webhooks/{webhook_id}")

Tool Definition Quality

A3.6/5.0
Behavior3/5

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

Annotations confirm destructive behavior (destructiveHint: true), and the description is consistent with this. However, beyond confirming the Codemagic context, it adds minimal behavioral detail—no mention of immediate vs. delayed deletion, side effects, or return value for a destructive operation.

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?

Front-loaded single-sentence description followed by structured Args block. No redundant text; every line serves either the purpose statement or parameter documentation. Slightly clinical Python-docstring style is efficient but less readable than prose.

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 low-complexity 2-parameter tool: the Args block compensates for zero schema coverage and the destructive annotation covers safety hints. However, lacks mention of return value or success confirmation expected from a delete operation.

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?

With 0% schema description coverage, the Args block effectively compensates by documenting both 'app_id' (Codemagic application ID) and 'webhook_id' (the ID to delete), clarifying the purpose of each parameter beyond their titles.

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?

Specific verb 'Delete' + resource 'webhook' + scope 'Codemagic application' clearly identifies the operation. Explicitly distinguishes from siblings like delete_app, delete_variable, and delete_cache by specifying the target resource type.

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 on when to use this tool versus alternatives, nor prerequisite steps (e.g., obtaining webhook_id via list_webhooks first). The Args block documents parameters but doesn't provide workflow context.

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