Skip to main content
Glama

List Webhooks

list_webhooks
Read-only

List the webhooks registered on the account: each one's id, event and receiving URL. Call this before register_webhook to avoid creating a duplicate, and to find the id needed by delete_webhook. 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
dataYesRaw Mobile Text Alerts API response envelope. The webhooks are nested under `data.data.rows`, with paging in `data.data.page`, `data.data.pageSize` and `data.data.total`.
errorNo
statusYes
successYes
statusTextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces the safety profile by noting secrets are never returned — a useful trust-boundary disclosure beyond the annotation. It does not mention pagination or result size limits, which is the main remaining gap for a list operation.

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?

Single sentence pair with zero filler: what it returns comes first, then the two concrete workflow reasons to call it, then a security note. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 already defined, the description supplies the missing workflow context (dedupe check, id lookup) and the secrecy guarantee. Nothing an agent needs to call it correctly is absent.

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 nothing to document; baseline 4 applies. The description instead spends its words on returned fields, which is the higher-value information here.

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?

States a specific verb and resource ('List the webhooks registered on the account') and enumerates the returned fields (id, event, receiving URL). It is clearly distinguishable from sibling mutations like register_webhook and delete_webhook.

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?

Gives explicit when-to-use guidance tied to named siblings: call before register_webhook to avoid duplicates, and to obtain the id needed by delete_webhook. The agent knows exactly which step this tool occupies in the workflow.

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