AWSYS Links

Create Webhook

create_webhook

Subscribe to link events by registering a webhook endpoint. Requires Pro (2 max) or Builder (10 max).

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"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	HTTPS endpoint that will receive POST requests
`name`	No	Optional display name for this webhook
`events`	Yes	Event types: link.click, link.created, link.updated, link.deleted, link.expired, link.limit_reached, link.geo_blocked

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuine value with plan-based quota limits, which an agent cannot infer otherwise. It does not say whether the endpoint is verified/validated, whether a test event is dispatched, or what happens when the quota is exceeded.

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 short sentences with zero filler; the core action comes first and the quota constraint second. Every sentence carries information an agent needs.

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?

For a three-parameter create tool with complete schema documentation and annotations covering the safety profile, the description supplies the key operational constraint (plan caps). Only minor gaps remain: quota-exceeded behavior and whether the endpoint must respond to verification.

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 description coverage is 100%, so the schema already documents url, name, and the full event-type list, making the baseline 3. The description does not contradict or duplicate this and correctly frames the required inputs at a high level, though it adds no specific syntax or format detail beyond the schema.

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?

Specific verb and resource: "Subscribe to link events by registering a webhook endpoint" makes clear this creates a webhook subscription rather than listing, testing, or updating one. Sibling tools like list_webhooks and test_webhook are implicitly distinguished by the create framing, though none are named.

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

Usage Guidelines3/5

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

The plan quotas (Pro 2 max, Builder 10 max) tell the agent when this call will succeed or fail, which is useful eligibility guidance. However, there is no explicit routing advice — nothing says when to use this versus test_webhook afterward or update_webhook for an existing endpoint, so usage is only implied by the verb.

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

All AWSYS Links tools Inspect

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

Need Help?