Reach MCP

create_webhook_endpoint

Register a URL to be called when something happens on LinkedIn, so an agent or an n8n/Make workflow can react instead of polling. Returns the signing secret ONCE; deliveries carry 'Reach-Signature: t=,v1=<hex HMAC-SHA256(secret, t + '.' + body)>'. Events: message.received, page.message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached, or '*' for all. Omit account_ids to subscribe for every account of the user. https only. Use when the user wants to react to a reply, a new connection, a quota alert or a job event from n8n, Make or their own code; needs an https URL they control. Not for the model to call itself.

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

Input Schema

Name	Required	Description
`url`	Yes	https URL that accepts a JSON POST.
`events`	Yes	Event types, or ['*'].
`account_ids`	No	Optional: only these LinkedIn account ids.
`description`	No	Free-text label for your own reference.
`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
`id`	No
`url`	No
`note`	No
`events`	No
`secret`	No	Signing secret, returned once
`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.

First observedSep 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false); the description adds non-obvious behavior well beyond that: the signing secret is returned exactly once, the exact 'Reach-Signature: t=...,v1=<hex HMAC-SHA256>' delivery format, the full event vocabulary, and the meaning of omitting account_ids. The https-only constraint is also a real operational constraint not implied by annotations.

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?

Purpose and the react-instead-of-polling rationale are front-loaded, and the dense signature/event details come after. Every sentence carries information, though the signature-format clause is heavy enough that the block reads more like a reference note than a crisp definition; slight tightening would help.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, yet the description still flags the one return detail an agent must not miss (the secret is shown only once). With event enumeration, scoping behavior, transport requirement, and the self-call exclusion all covered, nothing needed for correct invocation is missing.

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 100%, so a baseline of 3 would be defensible, but the description genuinely adds meaning: it enumerates the valid event strings (message.received, page.message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached), explains '*' as all events, and clarifies that omitting account_ids subscribes across every account of the user. Those are semantics the schema's terse 'Event types, or ["*"]' does not convey.

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?

States a specific verb and resource ('Register a URL to be called when something happens on LinkedIn') and immediately frames the outcome (react instead of polling). It is clearly distinguishable from list_webhook_endpoints, test_webhook_endpoint, update_webhook_endpoint and delete_webhook_endpoint, which are the relevant siblings.

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?

Gives concrete when-to-use triggers ('react to a reply, a new connection, a quota alert or a job event from n8n, Make or their own code'), states the prerequisite ('needs an https URL they control'), and adds an explicit exclusion ('Not for the model to call itself'). Both the positive and negative routing conditions are spelled out.

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?