Skip to main content
Glama

get_webhook

Fetch a single webhook endpoint by uuid (url, events, status; never the signing secret). Use it when you already know the uuid; to discover endpoints use list_webhooks. Requires the webhooks:read scope.

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": {
      "webhook_uuid": "<webhook_uuid>"
    },
    "name": "get_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_uuidYesPublic UUID of the webhook endpoint, as returned by create_webhook or list_webhooks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the returned fields and, importantly, that the signing secret is never included, plus the auth scope requirement. It stops short of stating what happens on an unknown uuid (e.g., 404 vs empty result), which is the remaining gap for a no-annotation tool.

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?

Three short clauses, front-loaded with the action and lookup key, then returned fields, then the routing rule and scope. Nothing is padded.

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?

No output schema exists, and the description compensates by naming the returned fields and the excluded secret; auth scope and the alternative tool are also covered. Only the error/not-found path is undisclosed, which is a minor omission for a simple single-record read.

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?

The single parameter has 100% schema description coverage, including the note that the UUID comes from create_webhook or list_webhooks, so the schema already does the work. The description's 'by uuid' phrasing is redundant with the schema rather than additive, making 3 the baseline.

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 (fetch) plus resource (single webhook endpoint) plus the lookup key (uuid), and it enumerates the returned fields (url, events, status). It explicitly distinguishes itself from list_webhooks, so an agent can route correctly without opening either schema.

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?

States the selection condition directly: 'Use it when you already know the uuid; to discover endpoints use list_webhooks.' It also names the required webhooks:read scope, which is a real precondition for invocation.

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.

Resources