hevy-mcp

delete_webhook_subscription

Remove the current webhook subscription to stop receiving updates.

Instructions

Delete the active webhook subscription.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_webhook_subscription"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/hevy_mcp/tools/webhooks.py:30-35 (handler)

The handler function for the delete_webhook_subscription tool. It sends a DELETE request to '/webhook-subscription' endpoint via the Hevy API client and returns a confirmation message.

@mcp.tool()
@tool_guard
async def delete_webhook_subscription() -> dict[str, Any]:
    """Delete the active webhook subscription."""
    await client.delete("/webhook-subscription")
    return {"text": "Webhook subscription deleted."}

src/hevy_mcp/tools/__init__.py:6-12 (registration)

Top-level registration entry point that calls webhooks.register(mcp, ctx), which in turn registers the delete_webhook_subscription tool via the @mcp.tool() decorator.

def register_all(mcp, ctx) -> None:
    workouts.register(mcp, ctx)
    routines.register(mcp, ctx)
    folders.register(mcp, ctx)
    templates.register(mcp, ctx)
    webhooks.register(mcp, ctx)
    analytics.register(mcp, ctx)

src/hevy_mcp/tools/webhooks.py:10-11 (registration)
The register() function in webhooks.py that registers all webhook tools (including delete_webhook_subscription) onto the FastMCP server using the @mcp.tool() decorator.
```
def register(mcp, ctx) -> None:
    client = ctx.client
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description indicates a destructive operation ('Delete'), but with no annotations, it lacks details on irreversibility, cascading effects, or what happens if no active subscription exists.

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?

Single sentence, zero waste, perfectly concise for a simple deletion operation.

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?

Minimal description is adequate for a param-less tool with an output schema, but omits context like the need for an existing subscription and return value explanation.

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?

There are no parameters, so the description adds no parameter information beyond the empty schema. Baseline 4 is appropriate for zero parameters.

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 'Delete the active webhook subscription,' specifying the verb (delete) and resource (active webhook subscription). It distinguishes from sibling tools like 'create_webhook_subscription' and 'get_webhook_subscription'.

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. It does not mention prerequisites (e.g., a subscription must exist) or exclusion conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.