Skip to main content
Glama
Hermoso

Hermoso

Official

List LinkedIn lead webhooks

list_linkedin_lead_subscriptions
Read-onlyIdempotent

List the lead notification webhooks registered on a LinkedIn Page or ad account, returning the subscription IDs needed for deletion.

Instructions

The lead notification webhooks registered on a LinkedIn Page or ad account, with the id delete_linkedin_lead_subscription takes. Read-only, free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_linkedin_lead_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNothe company Page that owns the form — from list_linkedin_pages; omit when one Page is shared
leadTypeNoSPONSORED for an ad account; COMPANY, EVENT or ORGANIZATION_PRODUCT for a Page; defaults by owner
adAccountIdNoread forms owned by an AD ACCOUNT instead of a Page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / leadType / description
      Added value: +"SPONSORED for an ad account; COMPANY, EVENT or ORGANIZATION_PRODUCT for a Page; defaults by owner"
  2. Addedv0.1.209

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' restates structured data. 'Free' is genuinely additive (cost transparency not in annotations) and the reference to the delete consumer clarifies the read-only nature of the resource. No mention of pagination, return shape, or what a subscription represents.

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?

A single dense sentence fragment with no filler; the deletion-id purpose is front-loaded at the end of the lead clause. Slightly awkward as a noun phrase that lacks a leading verb, but nothing is wasted.

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 zero-required-param read tool with full schema coverage and safe annotations, the description covers what the resource is and why you'd read it. It stops short of explaining what a subscription/webhook contains or how results are ordered, but no output schema exists to relieve that gap.

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 three parameters (pageId, leadType, adAccountId) are already fully documented in the schema. The description's 'on a LinkedIn Page or ad account' echoes the mutually exclusive owner scoping but adds no syntax, defaults or format detail beyond the schema.

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 title and description state the resource precisely — lead notification webhooks registered on a LinkedIn Page or ad account — and even name the downstream consumer of the returned ids (delete_linkedin_lead_subscription). It doesn't distinguish itself from near siblings like list_linkedin_lead_forms, list_linkedin_leads or subscribe_linkedin_leads, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

The clause 'with the id delete_linkedin_lead_subscription takes' implicitly tells the agent why to call this: to discover webhook ids before deleting them. Beyond that coupling there is no explicit when-to-use, no exclusion against the other LinkedIn lead tools, and no prerequisite info.

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