Skip to main content
Glama
Upload-Post

Upload-Post

Official

List webhook deliveries

list_webhook_deliveries
Read-only

Review webhook delivery history from the last 7 days to check whether Upload-Post events reached your server, with statuses, attempts, errors, and retry timing.

Instructions

History of the webhook events Upload-Post sent to the user's own webhook URLs over the last 7 days, newest first: account and profile webhooks, every event (upload_completed, social_account_connected / _disconnected / _reauth_required, dm_received, comment_received). Use it to find out whether an event reached the user's server: each delivery has status (pending = waiting for a retry, delivered, failed, cancelled), attempt_count / max_attempts, last_status_code or last_error (timeout, connection_error, HTTP nnn), every attempt in attempts, and next_attempt_at. Failed deliveries (timeout, connection error, 5xx, 408, 429) are retried automatically up to 6 attempts in about 8.5 hours; other 4xx answers are final. Test sends are marked test: true and never retried. The event body is left out unless include_payload is true; get_webhook_delivery returns one delivery with its body. Paginated with page (up to 50) and limit; the response carries total and has_more.

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_webhook_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-50. Default 1. To look further back, narrow the list with status, event or request_id.
eventNoOnly this event, e.g. 'upload_completed', 'dm_received', 'comment_received'.
limitNoDeliveries per page, 1-100. Default 20.
job_idNoOnly deliveries about this scheduled/queued `job_id`.
statusNoOnly deliveries in this state.
request_idNoOnly deliveries about this upload `request_id`.
include_payloadNoInclude each delivery's exact JSON body in `payload`. Default false.
profile_usernameNoOnly deliveries about this Upload-Post profile.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.23.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint true, destructiveHint false, closed world), yet the description still adds substantial behavior: retry policy (up to 6 attempts over ~8.5 hours for timeout/connection/5xx/408/429, other 4xx final), test sends marked `test: true` and never retried, the 7-day retention window, and the fact that payloads are omitted unless requested. That is exactly the kind of context the annotations cannot carry.

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?

The governing scope (7-day history, newest first) comes first, followed by diagnostic use, delivery-state fields, retry policy, payload behavior, and pagination – a logical front-loaded order with no filler. It is dense and long for one paragraph, and the retry/field enumeration could have been tightened or bulleted, but every sentence carries operational 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 an 8-parameter, fully optional-parameter read tool with an output schema, the description covers retention window, ordering, the meaning of each delivery state, retry semantics, payload opt-in, and pagination with `total`/`has_more`. Return-value details can be left to the output schema, so nothing an agent needs to call it correctly is missing.

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; the description nevertheless adds meaning by explaining that `include_payload` gates inclusion of the event body, and by tying `page` to the narrowing strategy via status/event/request_id once results exceed 50 pages. The remaining filters (status states, event names) are largely restated from the schema, so it does not go far beyond the baseline.

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?

The description states a specific verb and resource (list webhook delivery history of Upload-Post events sent to the user's own webhook URLs), fixes the scope (last 7 days, newest first), and enumerates the covered event types. It also explicitly separates itself from get_webhook_delivery, which returns a single delivery with its body.

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?

'Use it to find out whether an event reached the user's server' gives a concrete diagnostic use case, and 'get_webhook_delivery returns one delivery with its body' routes the agent to the right sibling for single-record/payload lookups. It does not point at redeliver_webhook for acting on failed deliveries or state any exclusion beyond that, so it falls short of a full when/when-not map.

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

Deploy Server

Other Tools