Reach MCP

update_webhook_endpoint

Idempotent

Change a webhook's url, events, account_ids, description or is_active. Only provided fields change. Re-enabling clears the failure counter. Use to change events, accounts or url, or to re-enable an endpoint disabled after failures; to stop deliveries temporarily set is_active=false rather than deleting.

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": {
      "endpoint_id": "<endpoint_id>"
    },
    "name": "update_webhook_endpoint"
  }
}

Input Schema

Name	Required	Description
`url`	No	https URL that receives the signed JSON POST (http accepted for localhost only).
`events`	No	Event types to subscribe to (message.received, page.message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached) or ['*'].
`is_active`	No	Pause (false) or resume (true) deliveries.
`account_ids`	No	Only these LinkedIn account ids; omit for every account of the user.
`description`	No	Free-text label for your own reference.
`endpoint_id`	Yes	Webhook endpoint id, from list_webhook_endpoints.
`idempotency_key`	No	Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedIn. Reusing a key with different arguments is refused. Keys expire after 24 hours.

Output Schema

Name	Required	Description	Default
`id`	No
`url`	No
`events`	No
`is_active`	No
`created_at`	No
`account_ids`	No
`description`	No
`disabled_reason`	No
`last_delivery_at`	No
`consecutive_failures`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / events / description

Previous value: -"Event types to subscribe to (message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached) or ['*']."New value: +"Event types to subscribe to (message.received, page.message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached) or ['*']."

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-open-world semantics, so the description's job is to add context beyond that — and it does: partial-update behavior ("Only provided fields change") and the side effect that "Re-enabling clears the failure counter" are not derivable from annotations or schema. It does not discuss failure modes or what an update to events does to in-flight deliveries, which keeps it short of a 5.

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?

Three compact sentences, front-loaded with the mutable field list and immediately followed by the partial-update rule and the routing guidance; no filler. Slightly dense in the second half but every clause carries information.

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, full schema coverage, and annotations carrying the safety profile, the description supplies what structured fields cannot: partial-update semantics, the re-enable side effect, and the pause-vs-delete rule. Only the effect of subscription changes on delivery history is left implicit.

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 description coverage is 100%, so every parameter including idempotency_key is already documented in the schema; the description only lists field names without adding format, ordering, or validation meaning. Baseline 3 applies when the schema carries the parameter burden.

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?

Opens with a specific verb and resource ("Change a webhook's url, events, account_ids, description or is_active") and enumerates the mutable surface, which separates it cleanly from create_webhook_endpoint, delete_webhook_endpoint and test_webhook_endpoint.

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

Usage Guidelines5/5

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

Explicitly states the selection condition ("Use to change events, accounts or url, or to re-enable an endpoint disabled after failures") and names the alternative behavior to prefer for a different goal ("to stop deliveries temporarily set is_active=false rather than deleting"). This routes the agent away from delete_webhook_endpoint without ambiguity.

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

All Reach MCP 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?