Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

List Webhooks

list_webhooks
Read-only

List webhook endpoints registered for your API key or environment to verify current integrations; signing secrets are never returned.

Instructions

List the webhook endpoints registered for THIS API key / environment (signing secrets are never returned).

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

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is to add context. It does: results are scoped per API key/environment, and signing secrets are explicitly never returned, which prevents an agent from planning on retrieving secrets from this call. No pagination or ordering behavior is disclosed, keeping it short of a 5.

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?

A single front-loaded sentence with no filler. Both clauses carry information an agent needs, and the secret-handling caveat is placed inline where it will be read.

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?

An output schema exists, so return values need not be described. Annotations carry the safety profile and the description adds scoping plus the secrets caveat. The only meaningful omission is result-set behavior (whether all endpoints are returned or pagination applies).

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 zero parameters, so the baseline is 4. The description correctly frames the implicit scoping (API key/environment) rather than implying any filter inputs exist.

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?

States a specific verb and resource ('List the webhook endpoints') and adds scope ('registered for THIS API key / environment'), which distinguishes it from the mutating siblings create_webhook and delete_webhook without naming them.

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?

Usage is implied: call this to enumerate existing webhook endpoints. There is no explicit when-to-use vs. when-not guidance or pointer to related tools such as get_webhook or create_webhook, which an agent investigating webhook state might otherwise need.

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