Skip to main content
Glama
Sign In

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

Create Webhook

aidelly_create_webhook

Create a webhook subscription for post lifecycle and inbox events (including inbox.lead.captured from the AI DM agent).

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyNoOptional body override for endpoints with sparse parameter schemas.
queryNoOptional query overrides for endpoints with sparse parameter schemas.
eventsNo
secretNo
brand_idNo
descriptionNo
workspace_idNoWorkspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "post.created",
-  "post.scheduled",
-  "post.published",
-  "post.failed",
-  "post.canceled"
-]New value: +[
+  "post.created",
+  "post.scheduled",
+  "post.published",
+  "post.failed",
+  "post.canceled",
+  "inbox.item.created",
+  "inbox.lead.captured"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / idempotency_key / example
      Added value: +"order-123:create-post:v1"
    • addedInput schema / properties / idempotency_key / maxLength
      Added value: +255
    • addedInput schema / properties / idempotency_key / minLength
      Added value: +1
    • addedInput schema / properties / idempotency_key / pattern
      Added value: +"^[\\x21-\\x7E]{1,255}$"
  3. Changed1 schema field changed
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Workspace to operate in. Do not ask the user for this UUID — call aidelly_list_workspaces and use the `id` of the matching workspace. Optional for read operations; required when creating content."New value: +"Workspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content."
  4. Changed1 schema field changed
    • addedInput schema / properties / workspace_id / description
      Added value: +"Workspace to operate in. Do not ask the user for this UUID — call aidelly_list_workspaces and use the `id` of the matching workspace. Optional for read operations; required when creating content."
  5. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the safety burden is partly lifted. The description adds useful context that the subscription covers post lifecycle and inbox events, but says nothing about the signing secret, retry/delivery behavior, or that a required idempotency_key must be supplied even though idempotentHint=false.

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?

A single front-loaded sentence with no filler; the parenthetical example earns its place. It is arguably too terse for a 9-parameter creation tool, though that shortfall is better counted against completeness.

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

Completeness2/5

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

For a 9-parameter, nested-object creation tool with no output schema and thin schema coverage, the description is substantially incomplete. It omits the required idempotency_key, the secret used for payload signing, workspace scoping, and default event behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 9 parameters and only 33% schema description coverage, the description needs to compensate and does not. It only loosely gestures at the events parameter ('post lifecycle and inbox events') and leaves url, secret, brand_id, description, and idempotency_key undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Create a webhook subscription') and narrows the scope to post lifecycle and inbox events, including a concrete example event (inbox.lead.captured). Sibling differentiation (delete_webhook, list_webhooks, list_webhook_deliveries) follows from the name rather than being spelled out in the description.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g. needing a workspace or a reachable endpoint), and no named alternative or condition that would steer the agent elsewhere. The event scope hints at intent but implies rather than states usage.

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

All aidelly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources