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

linkedin-mcp-server

by isucorp-taimiralain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_get_profile

Fetch the authenticated user's LinkedIn profile information, including name, email, and profile picture, to display or manage account data directly through the API.

Instructions

Get the authenticated user's LinkedIn profile information including name, email, and profile picture.

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": "linkedin_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden of transparency. It discloses that the profile is the authenticated user's, implying OAuth context, but does not mention read-only status, potential errors, or side effects. This is moderate transparency for a simple getter.

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?

The description is a single, clear sentence with no filler words. It front-loads the verb and resource, and every word adds meaning. Highly concise and well-structured.

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 tool with no parameters and no output schema, the description provides the essential context: what data is returned. It could be improved by mentioning the response format or any authentication prerequisites, but it is complete enough for a simple profile getter.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The description adds value by listing what the returned profile includes, which serves as the output semantics. Baseline 4 is appropriate for zero-parameter tools.

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?

The description clearly states the action (get), the resource (authenticated user's LinkedIn profile), and specific included fields (name, email, profile picture). It distinguishes itself from sibling tools that focus on posts and connections count.

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?

The description implies usage when the authenticated user's profile data is needed, but it does not explicitly mention when to use this tool over alternatives or any exclusions. Since siblings are clearly different, the implied usage is acceptable but not explicit.

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