Skip to main content
Glama

Realtime: Update destination

webhook_update_destination
Destructive

Update a webhook destination URL, events or provider/account selection. Common n8n chain: create with Test URL -> receive mock event -> update same destination to Production URL. Nilyo recomputes authorized account_ids server-side.

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": {
      "destination_id": "<destination_id>"
    },
    "name": "webhook_update_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
eventsNoExact event types. Call webhook_list_available_events first when unsure. Do not invent event names.
enabledNo
runtimeNo
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_urlNoPublic HTTPS POST receiver URL supplied by the target runtime, without user:password@ credentials or #fragment. Never guess a URL.
destination_idYesNilyo webhook destination ID returned by webhook_create_destination/webhook_list_destinations. Never use the remote webhook endpoint ID directly.
auto_include_new_accountsNo

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. Changed4 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 / destination_id / description
      Previous value: -"Nilyo webhook destination ID returned by webhook_create_destination/webhook_list_destinations. Never use the Unipile endpoint ID directly."New value: +"Nilyo webhook destination ID returned by webhook_create_destination/webhook_list_destinations. Never use the remote webhook endpoint ID directly."
    • 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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered outside the text. The description still adds value annotations cannot: Nilyo recomputes authorized account_ids server-side, which tells the agent that account scope is re-validated rather than trusted from the payload. It omits one important behavior for a 9-param mutation: whether omitted fields are left unchanged or cleared.

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?

Two dense sentences with no filler: the mutable fields come first, then the workflow pattern, then the account_ids caveat. Nothing is redundant, though the embedded n8n example is runtime-specific and marginally narrows the tool's apparent audience.

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

Completeness3/5

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

For a destructive, non-idempotent mutation with 9 parameters and no output schema, the definition covers mutation scope and account authorization but leaves gaps: partial-versus-full update semantics, what a successful response contains, and whether changing request_url requires re-verification are all unstated.

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 56%, with events, providers, account_ids, request_url and destination_id already documented in the schema itself, including enum values and the 'call webhook_list_available_events first' warning. The description adds only the server-side account_id recomputation and the loose phrase 'provider/account selection', which restates parameters rather than explaining them. A 3 is right when the schema carries most of the semantic load.

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?

The description opens with a specific verb plus resource and enumerates the mutable surface: "Update a webhook destination URL, events or provider/account selection." That distinguishes it cleanly from webhook_create_destination and webhook_get_destination by verb alone, though it never names those siblings explicitly.

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?

It supplies a concrete when-to-use pattern: create with a Test URL, receive a mock event, then update the same destination to the Production URL. That is real guidance for choosing update over create, but it gives no when-not-to-use condition or any note about prerequisites such as the destination needing to exist first.

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.