Skip to main content
Glama

Account Webhooks

alterlab_webhook
Destructive

Manage account webhooks: HTTPS endpoints that receive signed events such as job.completed, batch.completed, monitor.changed, credits.low and run.* events. action=create needs url (events defaults to job.completed); the response carries the signing secret once, so store it. list returns your webhooks; get, update (replaces the fields you send), delete, test (sends a sample event_type) and deliveries (recent delivery attempts) take webhook_id. Secret rotation stays in the dashboard and REST API. Use webhook_url on a single request instead when you only need one callback. Cloud export, extraction templates, org and API key management, BYOK and workflow definitions have no MCP tool: they are dashboard/API only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "alterlab_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNocreate, update: HTTPS endpoint that receives events
nameNocreate, update: webhook name. Default 'My Webhook'
limitNodeliveries: page size. Default 50
actionYescreate, list, get, update, delete, test or deliveries
eventsNocreate, update: event types to subscribe to, e.g. ['job.completed', 'monitor.changed']. Default ['job.completed']
offsetNodeliveries: rows to skip. Default 0
statusNodeliveries: optional status filter
is_activeNoupdate: enable or disable the webhook
event_typeNotest: event type of the sample payload. Default job.completed
webhook_idNoget, update, delete, test, deliveries: webhook ID
include_inactiveNolist: include disabled webhooks. Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses several non-obvious behaviors: the signing secret is returned only once on create, update replaces rather than merges sent fields, and test dispatches a sample payload. It stops short of saying that delete is permanent or how many deliveries are retained, so a small gap remains.

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 action contract is front-loaded and each clause carries operational information. The closing list of unrelated dashboard-only features (export, templates, org/API keys, BYOK, workflows) is useful routing context but is a dense tacked-on sentence that could be trimmed.

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

Completeness4/5

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

With 11 parameters, no output schema, and one required action discriminator, the definition covers what each action needs and hints at returns ('list returns your webhooks', 'response carries the signing secret once'). It does not describe the shape of delivery records or list pagination, which is the main remaining gap.

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 coverage is 100%, so every parameter is already documented, and the description largely restates that mapping (url for create, events defaulting to job.completed, webhook_id for the id-scoped actions). It adds only one nuance beyond the schema — that update replaces sent fields — so the baseline of 3 applies.

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 names a specific verb and resource ('Manage account webhooks: HTTPS endpoints that receive signed events') and enumerates the concrete event types handled. It distinguishes this tool from the sibling-style alternative 'webhook_url on a single request' and from actions that are dashboard/REST only.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states the selection condition for the alternative explicitly: 'Use webhook_url on a single request instead when you only need one callback.' It also maps each action to its required identifier ('get, update, delete, test and deliveries take webhook_id') and rules out non-tool capabilities such as secret rotation and BYOK.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.