Skip to main content
Glama

Realtime: Create destination

webhook_create_destination
Destructive

Create a realtime event destination for this Nilyo user. Nilyo creates the endpoint server-side but ALWAYS restricts it to account IDs owned by this authenticated user. By default matching future accounts are automatically added. Explicit account_ids without a providers filter stay restricted to those accounts, even with auto_include_new_accounts=true. For n8n use its Test URL first, validate with a Development/Mock event, then update to Production URL. The endpoint signing secret is kept encrypted server-side and is never returned by MCP: never ask for it.

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": {
      "name": "<name>",
      "runtime": "<runtime>",
      "request_url": "<request_url>",
      "events": "<events>",
      "auto_include_new_accounts": "<auto_include_new_accounts>"
    },
    "name": "webhook_create_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
eventsYesExact event types. Call webhook_list_available_events first when unsure. Do not invent event names.
runtimeYes
providersNoOptional provider filter. google includes Gmail and outlook includes Microsoft accounts. With auto_include_new_accounts=true, Nilyo keeps this endpoint's account_ids synchronized when the user connects matching accounts later.
account_idsNoOptional explicit account IDs returned by list_connected_accounts. Nilyo rejects the whole request if any ID is not owned by the authenticated user.
request_urlYesPublic HTTPS POST receiver URL supplied by the target runtime, without user:password@ credentials or #fragment. Never guess a URL.
auto_include_new_accountsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / providers / items / enum
      Previous value: -[
      -  "linkedin",
      -  "whatsapp",
      -  "instagram",
      -  "telegram",
      -  "google",
      -  "outlook",
      -  "imap"
      -]New value: +[
      +  "linkedin",
      +  "whatsapp",
      +  "instagram",
      +  "facebook",
      +  "telegram",
      +  "google",
      +  "outlook",
      +  "imap"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / account_ids / description
      Previous value: -"Optional explicit Unipile account IDs returned by list_connected_accounts. Nilyo rejects the whole request if any ID is not owned by the authenticated user."New value: +"Optional explicit account IDs returned by list_connected_accounts. Nilyo rejects the whole request if any ID is not owned by the authenticated user."
    • changedInput schema / properties / events / description
      Previous value: -"Exact Unipile V2 event types. Call webhook_list_available_events first when unsure. Do not invent event names."New value: +"Exact event types. Call webhook_list_available_events first when unsure. Do not invent event names."
    • changedInput schema / properties / providers / description
      Previous value: -"Optional provider filter. google includes Gmail and outlook includes Microsoft accounts. With auto_include_new_accounts=true, Nilyo keeps this Unipile endpoint's account_ids synchronized when the user connects matching accounts later."New value: +"Optional provider filter. google includes Gmail and outlook includes Microsoft accounts. With auto_include_new_accounts=true, Nilyo keeps this endpoint's account_ids synchronized when the user connects matching accounts later."
  3. Changed1 schema field changed
    • changedInput schema / properties / request_url / description
      Previous value: -"Public HTTPS POST receiver URL supplied by the target runtime. Never guess a URL."New value: +"Public HTTPS POST receiver URL supplied by the target runtime, without user:password@ credentials or #fragment. Never guess a URL."
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the endpoint is created server-side, always restricted to the authenticated user's accounts, and the signing secret is encrypted and never returned ("never ask for it"). The auto_include_new_accounts interaction with explicit account_ids is a genuinely non-obvious rule. What is missing is any disclosure about the destructiveHint=true implication — e.g., whether creating a duplicate destination replaces an existing one, or whether the creation is reversible via webhook_delete_destination.

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?

Well front-loaded — what is created, then the mandatory ownership constraint, then parameter interaction rules, then the workflow tip, then the secret warning. Every sentence carries information, though the n8n-specific sentence is narrow for a tool with four other runtime enum values and slightly interrupts the general-purpose flow.

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 7-parameter mutating tool with no output schema, the description covers the highest-risk unknowns: who owns the resulting endpoint, how account scope behaves over time, and that the signing secret will never be surfaced. It does not say what the tool returns (e.g., a destination ID needed for later webhook_update_destination calls) or whether duplicate names/URLs are permitted.

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 57%, and the description compensates well for the gap: auto_include_new_accounts has no schema description yet its synchronization and restriction semantics are explained in prose, and account_ids is clarified as user-scoped. The runtime parameter's enum values are never explained (only the n8n path is hinted at), and name has no semantics anywhere, so coverage is not complete.

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 and resource ("Create a realtime event destination") plus the ownership scope ("for this Nilyo user"), which is more than the title alone conveys. It does not name the sibling it differs from, so an agent must infer that modifying an existing endpoint is webhook_update_destination and that webhook_list_available_events precedes event selection.

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 operational context: use the n8n Test URL first, validate with a Development/Mock event, then update to Production. The account_ids vs providers filtering rules also act as usage guidance for parameter combinations. It stops short of explicit tool-selection guidance (when to use this versus webhook_update_destination or webhook_delete_destination).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.