Form4API — SEC Insider Trading

list_webhooks

Read-only

List webhook subscriptions owned by the authenticated API key. Returns active webhook subscriptions under the authenticated API key, plus any the system auto-disabled after sustained delivery failures (disabledReason "delivery_failures") — those stay visible with disabledAt/disabledReason set so you can see why delivery stopped and reverse it with POST /v1/webhooks/{id}/enable. Subscriptions you deleted yourself (disabledReason "user_deleted") are never returned here again, and neither are legacy rows disabled before this field existed (disabledReason null) — both are permanently gone from this list. Each entry: subscription id, target URL, subscribed event types, creation date, active flag, disabledAt/disabledReason (both null while active), and the isReadOnly flag. Delivery health, all nullable: lastAttemptAt (when the most recent delivery attempt, first attempt or retry, finished; null if none yet), lastSuccessAt (when the most recent attempt that got a 2xx finished), lastStatusCode (HTTP status of the most recent attempt; null when no response was received, e.g. timeout or connection failure), and lastErrorClass (why the most recent attempt failed, null if it succeeded or none has been made: HTTP_4XX, HTTP_5XX, HTTP_OTHER, TIMEOUT, DNS, TLS, CONNECT_REFUSED, URL_REJECTED, CIRCUIT_OPEN or OTHER). These reflect only attempts made after this field was introduced; older subscriptions show null until their next attempt. authHeaderName is the name of the custom auth header sent with each delivery (null if none is set); its value is never returned. urlWarning is a string when the URL's host is a temporary tunnel or test host (for example trycloudflare.com, ngrok or webhook.site), otherwise null. Change a subscription's URL with PATCH /v1/webhooks/{id}. Does NOT return the signing secret again (it's shown once, at creation, by POST /v1/webhooks) — regenerate by deleting and recreating the subscription if it's lost. Requires a valid X-Api-Key (401 without one).

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=true; the description adds substantial context beyond them — the 401-without-X-Api-Key requirement, the permanent invisibility of deleted and pre-flag legacy rows, the nullability rules for every delivery-health field, the fact that 2xx vs no-response vs error class are distinguished, and that the signing secret is deliberately never returned.

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?

Front-loaded with the inclusion/exclusion rule, then organized roughly per field, with every sentence carrying information rather than restating the name. It is a dense unbroken block, though, and the finer points of lastErrorClass and urlWarning could be tightened or segmented for faster scanning.

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?

There is no output schema, so the description must carry the return contract — and it does, enumerating every entry field, the nullable delivery-health values, the enum of error classes, and the auth header caveat. An agent can both decide to call this and interpret the response without any other source.

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 there is nothing for the description to disambiguate beyond the implicit scoping to the authenticated API key, which it does state. Baseline 4 applies for a parameterless tool.

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 webhook subscriptions owned by the authenticated API key') and immediately narrows scope by naming exactly what is and isn't included (auto-disabled rows yes, user_deleted and legacy rows no). No sibling tool in this catalog lists webhooks, so the definition alone establishes what makes this endpoint distinct.

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?

Makes the conditions clear: use this to see current subscriptions and why delivery stopped, then route to POST /v1/webhooks/{id}/enable to reverse a failure, PATCH /v1/webhooks/{id} to change a URL, or delete-and-recreate to recover a lost signing secret. It stops short of an explicit 'use this instead of X' comparator because no competing list tool exists.

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

All Form4API — SEC Insider Trading 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.