Skip to main content
Glama
Hermoso

Hermoso

Official

List LinkedIn leads (form responses)

list_linkedin_leads
Read-onlyIdempotent

Retrieve LinkedIn lead gen form responses with each answer keyed by field, plus the campaign, creative, consents and test status. Filter by form, date window or test-only leads.

Instructions

The LEADS a LinkedIn lead gen form collected — every response with its answers keyed by field (firstName, lastName, email, company, …), the campaign and creative that produced it, the consents ticked, and whether it was a test lead. Newest first. Filter by formId, a since/until window (ISO date or epoch ms — LinkedIn takes epoch), or testLeadsOnly. THIS IS PERSONAL DATA: show it to the user, hand it to the CRM they name, never repeat it into a post or an unrelated tool. Pass start for the next page. 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_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoper page, max 100
sinceNoISO date or epoch milliseconds
startNooffset for the next page
untilNoend of the time window, ISO date or epoch milliseconds; omit for now
formIdNoonly this form (from list_linkedin_lead_forms)
pageIdNothe company Page that owns the form — from list_linkedin_pages; omit when one Page is shared
leadTypeNodefaults by owner: SPONSORED for an ad account, COMPANY (organic Page form) for a Page; EVENT for event forms. LinkedIn refuses SPONSORED on a Page owner
adAccountIdNoread forms owned by an AD ACCOUNT instead of a Page
formVersionNodefault 1
testLeadsOnlyNotrue returns ONLY test submissions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / until / description
      Added value: +"end of the time window, ISO date or epoch milliseconds; omit for now"
  2. Addedv0.1.209

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds material context on top — newest-first ordering, the personal-data handling policy ('never repeat it into a post or an unrelated tool'), pagination via start, and that the call is free. These are behavioral facts the annotations cannot express.

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?

Front-loads what a lead record contains before moving to filters, privacy and pagination — the right order for an agent deciding whether to call it. It is a long run-on sentence chain with caps emphasis and an ellipsis in the field list, which costs a little crispness but no sentence is truly wasted.

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 10-parameter read tool with no output schema, the description carries the important load: it describes the returned record shape, ordering, pagination and data-handling obligations. Minor gaps remain — no mention of the default page size or what happens when no formId/owner is supplied — but those are covered by schema descriptions.

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 100% and every parameter carries its own description (including the leadType default-by-owner rule and pageId sourcing), so the schema does the heavy lifting. The description only re-surfaces formId, since/until and testLeadsOnly and adds the pagination hint for start; it says nothing about limit, pageId, adAccountId or formVersion beyond what the schema already states.

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 ('The LEADS a LinkedIn lead gen form collected') and then enumerates the return payload — answers keyed by field, campaign/creative attribution, consents, test-lead flag. That level of specificity makes it clearly distinct from get_linkedin_lead (single lead) and list_linkedin_lead_forms (form definitions) without needing to name them.

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?

Gives concrete guidance on how to use it: filter by formId, a since/until window, or testLeadsOnly, and 'pass start for the next page' for pagination. It also prescribes what to do with the results (show to the user, hand to the named CRM). It does not name alternatives for single-lead or event-level lookups, so it stops short of explicit when-not-to-use routing.

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