Skip to main content
Glama

List inbound webhook URLs

writ_list_webhooks
Read-onlyIdempotent

The account's inbound webhook URLs and the automations they fire.

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

Input Schema

NameRequiredDescriptionDefault
webhook_trigger_idNoOnly this webhook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that the output couples URLs with the automations they trigger, which is modest context; it says nothing about pagination, ordering, or account scoping beyond 'the account's'.

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 compact sentence that front-loads the resource and appends the one useful extra detail (the linked automations). No filler, no redundancy.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a low-complexity, read-only list tool with no output schema, and annotations cover the safety profile, so the description's brevity is mostly acceptable. It still omits any statement of how the optional filter behaves and what the listing contains structurally, leaving minor gaps.

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 100% for the single optional parameter, so the schema already explains 'Only this webhook.' The description adds no additional syntax or semantics for webhook_trigger_id, so the baseline 3 applies.

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?

The description names the specific resource (account's inbound webhook URLs) and adds that results include the automations each URL fires, which distinguishes it from other list-style siblings. However, it is a bare noun phrase with no verb, so the 'list' operation is only conveyed by the tool name/title rather than the prose itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no pointer to any alternative tool (e.g. writ_wire_monitor or writ_expose_workflow_api, which are the closest webhook-related siblings). The agent must infer usage entirely from the name.

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.