Skip to main content
Glama
Sign In

HTML/CSS to Image API

by io.github.htmlcsstoimage
OverviewDiscussionsAdmin

List Webhooks

list_webhooks
Read-onlyIdempotent

Lists the organization's webhooks, including disabled webhooks. Returns endpoints, subscribed events, and parameters in item.data; secret parameter values and signing secrets are never returned. Pass item.pagination.next_page_start as page_start to continue; a null cursor marks the last page.

Input Schema

NameRequiredDescriptionDefault
countNoMaximum number of webhooks to return, from 1 to 100. Defaults to 10.
page_startNoOpaque cursor from item.pagination.next_page_start in the previous response. Pass it unchanged; omit for the first page.

Output Schema

NameRequiredDescriptionDefault
itemNoOperation result. Check success before using this value.
errorNoError details when the operation failed; null on success.
successNoWhether the operation succeeded. If false, inspect error before retrying.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / item / properties / data / items / description
      Previous value: -"A webhook's endpoint, subscriptions, and delivery parameters. Secret parameter values and the signing secret are never returned."New value: +"A webhook's endpoint, subscriptions, and delivery parameters. Secret parameter values are never returned. The signing secret is returned only when creating a webhook through the REST API."
    • addedOutput schema / properties / item / properties / data / items / properties / signing_secret
      Added value: +{
+  "description": "Signing secret for verifying deliveries. Returned only in the REST API create response, even when signing is disabled. Store it securely; updates, reads, lists, and MCP responses omit this field.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses three things annotations cannot: disabled webhooks are included in results, secret parameter values and signing secrets are redacted from the response, and pagination is cursor-based with a null cursor marking the final page. Those are exactly the behavioral facts an agent needs before trusting or looping on the output.

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?

Two sentences, front-loaded with what is listed and scoped, then response-shape and redaction facts, then pagination. No filler, and each clause carries distinct information.

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 two-parameter, annotation-covered read tool with an output schema, this description covers scope, redaction, and pagination termination—everything needed to call it correctly and to stop looping at the right time.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds the operational link between the cursor it returns (item.pagination.next_page_start) and the page_start input, telling the agent to pass it back verbatim—slightly more than the schema's per-field wording conveys on its own.

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 ('Lists the organization's webhooks') and immediately scopes it with 'including disabled webhooks', which distinguishes it from get_webhook and from the other list_* siblings operating on proxies, templates, and storage destinations.

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 rather than stated: an agent can infer this is the enumeration counterpart to get_webhook, but the description never says when to prefer it over get_webhook or over the sibling list_* tools, and names no exclusions or prerequisites.

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

All HTML/CSS to Image API toolsInspect
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.

Resources