Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Update Webhook

update_webhook
DestructiveIdempotent

Change a webhook's endpoint URL, subscribed events, or active state to control which AdaptlyPost notifications get delivered. Enable or disable deliveries and reset events to the default set.

Instructions

Change a webhook endpoint's URL or the events it receives, or turn it off or back on with active. Sending events replaces the list, and [] goes back to the default set. Turning on an endpoint that was turned off after failed deliveries starts sending again. Events that happen while an endpoint is off, or that a new events list leaves out, are never delivered later, and after a URL change the old URL receives nothing more, so confirm the change with the user first. Fails with 409 when the new URL is already registered. Needs the webhooks.manage permission.

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": {
      "id": "<id>"
    },
    "name": "update_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebhook id from list_webhooks or create_webhook
urlNoNew http(s) endpoint URL
activeNofalse stops deliveries, true resumes them
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 updated webhook. 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.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: events replacement semantics, [] restoring the default set, undelivered events while inactive being lost permanently, the old URL going silent after a change, and a 409 conflict path. These directly explain why destructiveHint is true and are exactly the consequences an agent must surface before calling.

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 action and field list, then consequences, then failure and permission. Every sentence carries information, though a few run long with multiple comma-joined clauses that could be split 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?

For a destructive, open-world mutation with an output schema already defined, the description covers data-loss consequences, permission requirements, conflict errors, and user-confirmation policy. Nothing an agent needs before invoking is absent.

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% and the schema already documents every parameter, so the baseline is 3. The description still contributes meaning: it frames events as a full replacement rather than a merge, and clarifies that active=false stops while true resumes, which sharpens how to set the values.

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?

Opens with a specific verb and resource ('Change a webhook endpoint's URL or the events it receives') and enumerates the full mutable surface including the active toggle. An agent immediately knows this is the mutation path for an existing webhook, distinct from create/get/delete siblings.

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?

Gives an explicit operative instruction — 'confirm the change with the user first' — plus the failure condition (409 on an already-registered URL) and the permission needed. It does not name siblings like delete_webhook or test_webhook as alternatives, but the mutation scope is unambiguous enough that the agent can self-route.

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