Skip to main content
Glama
Hermoso

Hermoso

Official

Stop a LinkedIn lead webhook

delete_linkedin_lead_subscription
DestructiveIdempotent

Delete a LinkedIn lead notification webhook to stop real-time delivery while keeping existing leads readable.

Instructions

Remove a lead notification webhook (subscriptionId from list_linkedin_lead_subscriptions). Leads themselves are unaffected and stay readable; only the real-time delivery stops. Read back from LinkedIn. Free.

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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "delete_linkedin_lead_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNothe company Page that owns the form — from list_linkedin_pages; omit when one Page is shared
adAccountIdNoread forms owned by an AD ACCOUNT instead of a Page
subscriptionIdYeswebhook id from list_linkedin_lead_subscriptions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / subscriptionId / description
      Added value: +"webhook id from list_linkedin_lead_subscriptions"
  2. Addedv0.1.209

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true. The description usefully adds that leads remain unaffected and readable, only delivery stops, and notes the action is read back from LinkedIn and free, which clarifies blast radius beyond the annotations.

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?

The description is front-loaded with the core action and then adds only the effect scope and cost context. Every sentence carries useful information for deciding whether to invoke the tool.

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 destructive webhook-removal tool with no output schema, the description covers what is removed, what is left intact, where the ID comes from, and cost. It could be slightly stronger by noting reversibility or prerequisites, but the annotations and schema cover most remaining behavioral needs.

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 the schema already fully documents subscriptionId, pageId, and adAccountId. The description repeats that subscriptionId comes from list_linkedin_lead_subscriptions but does not add new meaning for the optional pageId or adAccountId parameters.

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?

The description states a specific verb and resource: remove a lead notification webhook. It also immediately distinguishes the effect from deleting leads themselves, which is critical next to sibling tools like list_linkedin_lead_subscriptions and subscribe_linkedin_leads.

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?

Usage is clear: use this to stop real-time lead delivery for a subscription, with subscriptionId sourced from list_linkedin_lead_subscriptions. It does not explicitly state when not to use it or name subscribe_linkedin_leads as the inverse operation, though the context is strong.

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

Deploy Server

Other Tools