Skip to main content
Glama

Webhooks Show

webhooks_show

Retrieve details of a specific webhook by organisation ID and webhook ID, so you can inspect its configuration and status.

Instructions

Get details of a webhook. GET /organisations/{organisationId}/webhooks/{webhookId}

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": {
      "organisation_id": "<organisation_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "webhooks_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the HTTP method (GET) and the full path, which tells an agent this is a read-only, idempotent, organisation-scoped lookup, but it says nothing about failure modes (unknown webhook_id, wrong organisation), required permissions, or what 'details' are returned.

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?

Two short sentences, front-loaded with the purpose and followed by the endpoint. Nothing is padded, though the raw path duplicates what the name and schema already imply.

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?

This is a simple two-parameter read with no output schema, so the description should at least hint at what a webhook record contains or confirm that IDs must be known in advance. As written it is minimally adequate for calling the tool but leaves the return value entirely unspecified.

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 description coverage is 0%, so the description must compensate, and it partially does: the path template shows that organisationId and webhookId are hierarchical path segments, with the webhook nested under the organisation. It adds no format details (ID shape, where to obtain them), so the compensation is only marginal.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Get details of a webhook'), which cleanly separates a single-resource fetch from the list-style sibling webhooks_index and the mutating webhooks_create/webhooks_destroy. It stops short of explicitly naming those alternatives, but the singular 'a webhook' plus the ID-bearing path makes the distinction obvious.

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?

There is no guidance on when to call this versus webhooks_index (list all) or a show tool for another resource, nor any stated prerequisites such as needing a known webhook_id first. Usage is only implied by the tool name.

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