Skip to main content
Glama
Sign In
linkedin-mcp-pro

linkedin-mcp-pro

by horizonbymuneeb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_person_profile

Fetch a LinkedIn member's profile using their public identifier (vanity name) from profile URLs.

Instructions

Get a LinkedIn member's profile by their public identifier (vanity name).

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": {
      "public_id": "<public_id>"
    },
    "name": "get_person_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
public_idYesThe vanity name from a profile URL, e.g. 'satyam-code' from https://linkedin.com/in/satyam-code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the basic action without disclosing behavioral traits like authentication requirements, error handling, or profile visibility constraints.

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?

Single, clear sentence with no unnecessary words; front-loaded with key information.

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?

Adequate for a simple retrieval tool but lacks details on return values (no output schema) and potential prerequisites like auth scope or profile privacy settings.

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% with a clear example in the parameter description. The tool description reinforces that public_id is a 'vanity name', adding marginal value over the schema.

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?

Description explicitly states verb 'Get', resource 'profile', and method 'by public identifier (vanity name)', clearly differentiating from sibling tools like get_my_profile or search_people.

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?

While it implies use when you have a public identifier, there is no explicit guidance on when to use this tool versus alternatives (e.g., search_people) nor any exclusions or prerequisites.

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