Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Create Webhook

create_webhook

Register an HTTP endpoint to receive AdaptlyPost workspace events as POSTs, with chosen event subscriptions, signed payloads, and automatic retries for failed deliveries.

Instructions

Register a URL that receives workspace events as HTTP POSTs. Without events it gets the default set: post.published, post.partially_failed, post.failed, post.scheduled, account.unauthorized, image.completed and image.failed. To also get inbox events (comment.created, comment.replied, mention.created, message.received, review.created), list every event wanted in events, since a non-empty list means only those. Each delivery carries the x-adaptly-signature, x-adaptly-timestamp, x-adaptly-event and x-adaptly-webhook-id headers; the signature is sha256=HMAC_SHA256(secret, "{timestamp}.{rawBody}"). Failed deliveries are retried up to 5 times with exponential backoff, and an endpoint is turned off after 20 failed deliveries in a row. Returns the new webhook (id, url, active, events, createdAt, updatedAt, lastSuccessAt, lastFailureAt, disabledAt). The signing secret never comes back to you: the result carries secretRevealUrl, a link the user opens in their browser to see the secret once within 30 minutes (on a local install, secretFile, a file only the user can read). Give the user that link or path and do not open, fetch or read it yourself. If the user loses the secret, delete the webhook and create it again. Fails with 400 for an invalid URL or the webhook limit, and 409 when the URL is already registered. Needs the webhooks.manage permission, which Admin and Editor hold.

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>"
    },
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublicly reachable http(s) endpoint that receives the events
eventsNoEvents this endpoint receives. Omit it or send [] for the default set: post.published, post.partially_failed, post.failed, post.scheduled, account.unauthorized, image.completed and image.failed. The inbox events comment.created (a new comment from someone else), comment.replied (the account replied, from AdaptlyPost or the platform app), mention.created, message.received and review.created (a new Google review) reach only an endpoint that lists them. A non-empty list means only the listed events. Inbox events arrive within about 10 minutes, after the next inbox sync, and the first sync of an account fires none for its history
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesThe new webhook, plus where the user collects the signing secret. The webhook: id, url, active, events (empty means the default post, account and image events), createdAt, updatedAt, lastSuccessAt, lastFailureAt and disabledAt (set when it was turned off after 20 failed deliveries in a row).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false), the description discloses delivery headers, the exact HMAC signature construction, retry policy (5 attempts with exponential backoff), endpoint auto-disable after 20 consecutive failures, required permission, and 400/409 failure modes. The secret-handling paragraph is especially valuable: it explains that the secret is never returned and that the agent must hand the user secretRevealUrl or secretFile rather than reading it.

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 description is long but front-loaded and organized: purpose, default events, event-selection rule, delivery contract, return shape, secret handling, errors, permissions. A few sentences restate schema content (event defaults, return field list) that the output schema and input schema already provide, which is the only reason it is not a 5.

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 three-parameter creation tool with an output schema, the description covers everything an agent needs: what gets created, defaults, permission requirement, error codes, retry behavior, and the non-obvious secret-reveal constraint. It restates the return fields even though an output schema exists, but that is harmless surplus rather than a gap.

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 coverage is 100%, so both url and events are already fully documented, including the default-set rule and inbox-event semantics that the description repeats. The description adds no information about workspaceId, which the schema covers, and much of the events explanation is redundant with the schema text. This is the expected baseline when the schema does the heavy lifting.

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 first sentence gives a specific verb and resource — "Register a URL that receives workspace events as HTTP POSTs" — which unambiguously describes creation of a webhook endpoint. The word "Register" and the return of a new webhook distinguish it from update_webhook and test_webhook without needing to name them.

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?

It clearly states the default event set when events is omitted and the rule that a non-empty list means only those events, which is the main decision an agent faces. It also covers the secret-retrieval flow and tells the agent not to fetch the reveal link itself. It does not name sibling alternatives such as update_webhook or test_webhook, so the routing guidance is implicit.

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