Skip to main content
Glama
EgiStr

linkedin-mcp

by EgiStr

Get My LinkedIn Profile

linkedin_get_my_profile
Read-onlyIdempotent

Retrieve your authenticated LinkedIn profile details including name, headline, profile URL, email, and locale. Choose Markdown or JSON output.

Instructions

Get the authenticated user's LinkedIn profile information.

Returns your full profile details including name, headline, vanity URL, profile picture, email, and locale. Combines both the OpenID Connect userinfo endpoint and the LinkedIn profile API.

Args:

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns (JSON format): { "id": string, // LinkedIn member ID "firstName": string, // First name "lastName": string, // Last name "fullName": string, // Full display name "headline": string, // Professional headline "vanityName": string, // Custom URL identifier "profileUrl": string, // Full LinkedIn URL "email": string, // Email address (if available) "pictureUrl": string, // Profile picture URL "locale": string // Locale setting }

Requires scope: openid + r_liteprofile (or r_basicprofile)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description goes further by revealing that the tool combines the OpenID Connect userinfo endpoint and the LinkedIn profile API, requiring specific scopes, which is meaningful behavioral context beyond the 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?

The description is front-loaded with the main purpose and uses structured Args and Returns sections. It is a bit longer than strictly necessary due to duplicating the schema's parameter info, but the return-structure block earns its place since there is no output schema.

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?

With no output schema, the description compensates by enumerating every return field, the response format options, and scope requirements. It is complete enough for an agent to invoke the tool with confidence. Minor gaps like error scenarios or when email may be missing prevent a perfect score.

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 the schema already documents response_format with an enum, default value, and description. The description mostly restates that parameter. The detailed return-shape block is useful but relates more to output semantics than to deeper parameter meaning.

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 description clearly specifies the verb 'Get' and resource 'the authenticated user's LinkedIn profile information,' and the details about full profile data and endpoint composition make the purpose apparent. However, it never explicitly differentiates itself from the sibling linkedin_get_user_info, so it stops short of full sibling distinction.

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 description provides clear context for when to use the tool: whenever the authenticated user's own profile data is needed. It also notes the required OAuth scopes, which is valuable operational guidance, but it does not explicitly say when not to use this tool or name alternatives.

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

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/EgiStr/linkedin-mcp'

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