Skip to main content
Glama
Hermoso

Hermoso

Official

Read one LinkedIn lead

get_linkedin_lead
Read-onlyIdempotent

Retrieve a LinkedIn lead by ID and return each answer labeled by field for viewing only. Use IDs from list_linkedin_leads; read-only and free.

Instructions

One LinkedIn lead by id (from list_linkedin_leads), with every answer named by field. Personal data — show, never republish. Read-only, 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": {
      "leadId": "<leadId>"
    },
    "name": "get_linkedin_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadIdYeslead id from list_linkedin_leads
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / leadId / description
      Added value: +"lead id from list_linkedin_leads"
  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 cover the safety profile (readOnly, idempotent, non-destructive), and the description adds two things they cannot: a data-handling constraint ('Personal data — show, never republish') and cost ('free'). It stops short of describing what happens if the lead id doesn't exist or belongs to another Page, but the key behavioral caveats are present.

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?

Two short sentences with zero waste; the resource and scope are front-loaded and the handling/cost caveats follow. The clipped phrasing ('with every answer named by field') is slightly odd but still parses as a response-shape hint rather than filler.

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?

No output schema exists, and the description compensates by noting that answers are returned as named fields. Combined with the privacy constraint and the schema's complete parameter documentation, an agent has enough to call it correctly, though error behavior for an unknown or cross-Page lead id is unaddressed.

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%, so all three parameters including the Page-vs-ad-account distinction are already fully documented. The description only restates leadId's provenance, adding no extra meaning beyond the schema's own 'lead id from list_linkedin_leads'. Baseline 3 applies when the schema does the heavy lifting.

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 scope ('One LinkedIn lead by id') and anchors the id's origin to the sibling list_linkedin_leads, so an agent can distinguish it from list_linkedin_leads and list_linkedin_lead_events without opening a schema. The 'every answer named by field' clause signals the response is labeled rather than positional.

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?

The parenthetical '(from list_linkedin_leads)' tells the agent where the required id comes from, which effectively describes the correct call sequence. It does not explicitly say when to prefer list_linkedin_leads (e.g., over many records) or when pageId/adAccountId disambiguation is needed, leaving that to the schema.

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