Skip to main content
Glama
jbalbu01

sales-intelligence

by jbalbu01

Search LinkedIn Leads

linkedin_search_leads
Read-onlyIdempotent

Search for people/leads on LinkedIn using keywords, title, company, seniority, geography, and industry filters.

Instructions

Search for people/leads on LinkedIn using keywords, title, company, seniority, geography, and industry filters.

Uses the standard LinkedIn REST API (no SNAP partnership required). Works with any LinkedIn developer token that has the appropriate OAuth scopes.

Note: The standard LinkedIn API has more limited people search than Sales Navigator. For deep lead research, combine with ZoomInfo or Clay enrichment tools.

Args:

  • keywords (string, optional): Free-text search across profiles

  • first_name / last_name (string, optional): Name filters

  • title (string, optional): Job title filter

  • company_name (string, optional): Current company

  • industry (string, optional): Industry

  • geography (string, optional): Location/region

  • seniority (string, optional): 'owner', 'cxo', 'vp', 'director', 'manager', 'senior', 'entry'

  • limit (number): Max results (default: 20)

  • offset (number): Pagination offset

  • response_format ('markdown' | 'json')

Returns: Name, headline, title, company, location, industry, profile URL.

Examples:

  • "VP Engineering in Bay Area" -> title='VP Engineering', geography='San Francisco Bay Area'

  • "CTO at Acme Corp" -> title='CTO', company_name='Acme Corp'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default: 20)
titleNoCurrent job title (e.g. 'Chief Technology Officer')
offsetNoPagination offset
industryNoIndustry code or name
keywordsNoKeyword search across profiles (e.g. 'VP Engineering')
geographyNoGeographic region (e.g. 'San Francisco Bay Area')
last_nameNoLast name filter
seniorityNoSeniority level: 'owner', 'cxo', 'vp', 'director', 'manager', 'senior', 'entry'
first_nameNoFirst name filter
company_nameNoCurrent company name
response_formatNoOutput format: 'markdown' or 'json'markdown
Behavior4/5

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

Annotations already provide safety profile (readOnly, idempotent, non-destructive). Description adds operational context: uses standard LinkedIn API (no SNAP), requires OAuth scopes, and has limited people-search depth compared to Sales Navigator. No contradictions with 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?

Well-organized with clear sections: purpose, API context, args, returns, examples. Front-loaded with the main action. Some redundancy with schema's parameter descriptions, but the streamlined Args list and examples are useful without being overly verbose.

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?

For a tool with 11 optional parameters and no output schema, the description covers input semantics, return fields (name, headline, title, company, location, industry, URL), limitations, examples, and API prerequisites. This gives the agent sufficient context to invoke correctly and interpret results.

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 covers 100% of parameters with descriptions, setting a baseline of 3. The description adds value through natural-language mapping examples (e.g., 'VP Engineering in Bay Area' -> title/geography) and a compact consolidated Args list that helps the agent translate user intent into 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?

Specific verb+resource: 'Search for people/leads on LinkedIn' with enumerated filters (keywords, title, company, seniority, geography, industry). This clearly distinguishes it from sibling tools like linkedin_search_companies or linkedin_get_profile.

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?

Explicitly notes the limitation vs Sales Navigator and suggests combining with ZoomInfo/Clay for deep research. Also states API requirements (standard REST, OAuth scopes), giving agent guidance on when the tool is appropriate. Does not fully specify when-not-to-use but provides actionable context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jbalbu01/sales-intelligence-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server