Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Test Webhook

test_webhook

Sends a signed webhook.test event to a configured endpoint and reports its response, so you can verify the webhook URL and signature check work.

Instructions

Send one signed webhook.test event to the endpoint now and report how it answered, to check the URL and the signature check work. 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": "test_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebhook id from list_webhooks or create_webhook
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
resultYesAn object with success, statusCode (the HTTP status the endpoint answered) and error when the delivery failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description adds real behavioral context: exactly one event is fired, it happens immediately, it contacts an external endpoint, it reports the endpoint's response, and it requires the webhooks.manage permission. The permission requirement and the "one event" non-idempotent framing are valuable and not encoded in the structured fields.

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 tight sentences: the action and its verification purpose are front-loaded, and the permission requirement trails where it belongs. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be explained, and the description covers action, purpose, and permission. Minor gaps remain around failure behavior and rate-limit impact when many test events are fired, but nothing essential to invoking it is missing.

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% and both parameters are fully documented in the schema, including which sibling tools provide the id. The description adds no parameter-level detail such as payload format or per-call workspace scoping, so the baseline 3 applies.

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 ("send one signed webhook.test event to the endpoint") plus its purpose ("to check the URL and the signature check work"), which unambiguously separates it from the CRUD siblings like get_webhook or update_webhook.

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 clear context for when to call it: verifying the endpoint URL and signature check. It also states the prerequisite (webhooks.manage). It stops short of explicit exclusions or naming a sibling alternative, so it lands just below the top band.

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