Skip to main content
Glama

List webhooks

list_webhooks
Read-onlyIdempotent

List the company's webhook endpoints (admin only; Solo Lite 1 endpoint, Solo 3, Team and Business+ 10), including each signing secret, and the events you can subscribe to.

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
api_keyNoAn md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an "Authorization: Bearer <api_key>" header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your md2sign API key. Only needed if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."New value: +"An md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), yet the description still adds value: an authorization requirement (admin only), plan-tier quotas, and a disclosure that signing secrets are returned in the response — a security-relevant detail an agent should know before echoing output. It does not mention rate limiting or result-set size, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler; the resource and access constraint come first. The parenthetical plan-tier list is dense but each element carries real limit information, so little 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 read-only list tool with full annotation coverage and no output schema, the description covers access control, quotas, and return content, so an agent can decide and call correctly. Pagination or result-size behavior for a list endpoint is the only notable omission.

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?

There is a single api_key parameter with 100% schema coverage, and the schema already explains multi-account usage and the Bearer-header fallback. The description says nothing about api_key, so it adds no meaning beyond structured data — the baseline 3 applies.

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 ('List') and resource ('the company's webhook endpoints'), plus the exact payload content (signing secrets and subscribable events). The verb alone separates it from save_webhook, delete_webhook and the other write siblings without needing their schemas.

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?

'admin only' and the per-plan endpoint caps (Solo Lite 1, Solo 3, Team/Business+ 10) give the agent concrete preconditions for calling. It stops short of naming save_webhook or delete_webhook as the follow-up/alternative actions, so it is clear context rather than explicit routing.

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.