Skip to main content
Glama

List Event Webhooks

list_event_webhooks
Read-onlyIdempotent

List this event's webhook endpoints and subscribed events. Never returns signing secrets. Requires event host access. Read-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": {
      "event_id": "<event_id>"
    },
    "name": "list_event_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint, so the safety profile is established. The description adds two pieces of context not in the structured fields: the host-access authorization requirement and the guarantee that signing secrets are never returned, which prevents wasted attempts to recover secrets here.

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?

Four compact clauses, front-loaded with the resource and scope, with no filler. Slightly telegraphic style but every sentence carries information an agent needs.

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?

For a single-parameter read-only listing tool with no output schema, the description covers scope, authorization, and the key return-value caveat (no signing secrets), and it names the returned content (endpoints and subscribed events). Given the tool's simplicity, only minor gaps remain, such as pagination or result ordering.

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% for the single event_id parameter, so the description has to carry the meaning. "this event's" implies event_id identifies the target event, but no format, length, or constraint guidance is added beyond that hint, leaving the pattern and maxLength solely to the schema.

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?

"List this event's webhook endpoints and subscribed events" gives a concrete verb (List) and resource (webhook endpoints / subscribed events) scoped to a single event. It is clearly distinguishable from create_event_webhook and revoke_event_webhook by the read-only listing verb, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

"Requires event host access" is a useful precondition, and "Never returns signing secrets" implicitly tells the agent to look elsewhere for that data. However, there is no explicit when-to-use statement or named alternative for creating/revoking webhooks, so the routing guidance is only implied.

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.