Rizamo

List webhook endpoints

list_webhooks

Read-onlyIdempotent

Use this when the person asks where the team's events are delivered: each endpoint with the event types and profiles it takes and whether its deliveries work. Endpoints are made and changed in the web app or the REST API.

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": "list_webhooks"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`items`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: this endpoint cannot create or change webhooks, which pushes the agent to the web app or REST API instead of attempting a write. No rate limits or pagination are mentioned, but the key boundary is stated.

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 sentences, front-loaded with the usage trigger and with zero filler. The phrasing "where the team's events are delivered" is slightly indirect compared with simply saying it lists webhook endpoints, but nothing is wasted.

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 zero-parameter read tool with an output schema that already defines the return shape, the description covers intent, contents, and the out-of-band mutation path. The one gap is not pointing to list_webhook_deliveries for per-delivery detail, which matters given how close that sibling is.

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?

The tool takes no parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies an unfiltered, team-wide listing rather than a scoped query.

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?

Describes a specific resource (webhook endpoints) and what is returned for each: event types, profiles, and delivery health ("whether its deliveries work"). The verb is implied rather than stated, and there is no explicit differentiation from the sibling list_webhook_deliveries, so the picture is clear but not sibling-distinguishing.

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

Usage Guidelines4/5

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

"Use this when the person asks where the team's events are delivered" gives a concrete triggering intent, which is stronger than most. It also notes that endpoint creation/modification happens in the web app or REST API, implicitly excluding mutating use cases, but it never names list_webhook_deliveries as the alternative for per-delivery questions.

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

All Rizamo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?