Skip to main content
Glama
Upload-Post

Upload-Post

Official

Create a webhook subscription

create_webhook_subscription
Idempotent

Create a signed webhook subscription to receive selected Upload-Post events at a public URL, with preview-before-confirmation approval.

Instructions

Add a destination that receives the listed events (besides the account webhook), signed like the account webhook (X-Upload-Post-Signature with the account's webhook secret, plus X-Upload-Post-Subscription: ). Idempotent: the same url + events + profile_username returns the existing subscription (created: false) and reactivates it if it was disabled (reactivated: true); name and source are updated when sent. The first delivery can take about a minute; failed deliveries are retried and show up in list_webhook_deliveries. At most 10 active subscriptions per account (409 subscription_limit_reached). Team members cannot create them (403 team_member_forbidden). Events: upload_completed, social_account_connected, social_account_disconnected, social_account_reauth_required, dm_received, comment_received, telegram_update, review_received, review_updated, customer_media_received, listing_google_update, listing_duplicate, listing_control_changed, post_analytics_updated; also youtube_video_published / youtube_video_updated and the post approval events (post_approval_requested, post_approved, post_rejected, post_approval_expired) while those features are on. Not generally available yet: until webhook subscriptions are switched on for the account, every call answers 503 with reason webhook_subscriptions_disabled (the feature is off, not a temporary failure). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "events": "<events>"
    },
    "name": "create_webhook_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https URL that will receive the events.
nameNoFree label shown in the dashboard.
eventsYesEvent names, e.g. ['upload_completed', 'comment_received'].
sourceNoLabel of the integration creating it (a-z, 0-9, _ . -), e.g. 'n8n'.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
profile_usernameNoOnly events of this Upload-Post profile. Without it: every profile of the account.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the signature scheme (X-Upload-Post-Signature plus X-Upload-Post-Subscription), the exact idempotency key (url + events + profile_username) with the `created: false` and `reactivated: true` outcomes, that name/source are overwritten on repeat calls, and that first delivery lags ~a minute with retries. These are the mutation and side-effect details an agent needs but that readOnlyHint/idempotentHint/destructiveHint alone do not convey.

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 purpose, then idempotency, then error/limit conditions, then the event catalog, then the approval protocol — a sensible ordering for an agent. It is dense and the long event enumeration plus feature-flag parenthetical are heavy, but nearly every clause carries operational information rather than restating the schema.

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 6-parameter mutation with an output schema already documenting return values, the description covers the remaining gaps: auth constraints, quota, feature gating, delivery latency, retry behavior, and the mandatory preview-then-confirm flow. Nothing an agent needs in order to call this 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, but the description adds real semantics the schema lacks: which fields participate in the idempotency key, that name and source are updated rather than ignored on a repeat call, and the gating role of `confirmed`. The full enum of valid event names is a meaningful supplement to an unenumerated free-string `events` array.

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?

Specific verb+resource ("Add a destination that receives the listed events") with immediate disambiguation from the account webhook ("besides the account webhook") and a pointer to the sibling that inspects results (list_webhook_deliveries). An agent can identify this as subscription creation rather than deletion, testing, or delivery listing without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use and when-not-to-use conditions: not available to team members (403 team_member_forbidden), capped at 10 active subscriptions (409 subscription_limit_reached), and hard-blocked with 503 webhook_subscriptions_disabled while the feature is off, with the note that this is a permanent feature flag, not a transient failure. It also prescribes a two-call approval protocol (preview without `confirmed`, then `confirmed: true`), which no sibling requires.

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