Skip to main content
Glama
felipfr

LinkedIn MCP Server

by felipfr

get_my_profile

Retrieve LinkedIn profile details using OpenID Connect and standard OAuth scopes, enabling access to user data for integrations and analytics.

Instructions

Get my LinkedIn profile information using OpenID Connect - works with standard OAuth scopes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the tool logic by making an authenticated GET request to the LinkedIn /me endpoint to retrieve the current user's profile.
    public async getMyProfile(): Promise<LinkedInProfile> {
      return this.makeRequest<LinkedInProfile>('get', '/me?projection=(id,firstName,lastName,headline,profilePicture)')
    }
  • Input schema for the get-my-profile tool, which is empty as no parameters are required.
    emptyParams: {},
  • src/server.ts:144-157 (registration)
    MCP tool registration for 'get-my-profile', specifying name, description, schema, and wrapper handler that delegates to ClientService.getMyProfile() and formats the response.
    this.server.tool(
      'get-my-profile',
      "Retrieve the current user's LinkedIn profile information",
      linkedinApiSchemas.emptyParams,
      async () => {
        this.logger.info('Retrieving Current User Profile')
        try {
          const profile = await this.clientService.getMyProfile()
          return this.createResourceResponse(profile)
        } catch (error) {
          this.logger.error('Current User Profile Retrieval Failed', error)
          throw error
        }
      }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions authentication requirements ('OpenID Connect,' 'OAuth scopes'), which is valuable context. However, it doesn't describe what specific profile information is returned, potential rate limits, or error conditions.

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, efficient sentence that conveys the core purpose and key operational context (OpenID Connect, OAuth scopes) without any wasted words. It is appropriately sized and front-loaded with essential 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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It covers authentication context but doesn't specify what profile data is returned or how it differs from the 'get_profile' tool, leaving some ambiguity for an AI agent.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose and context without redundant parameter information, earning a baseline score of 4 for zero-parameter tools.

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 states the action ('Get') and resource ('my LinkedIn profile information'), making the purpose understandable. However, it doesn't explicitly distinguish this from the sibling 'get_profile' tool, which appears to be a more general profile retrieval tool.

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 context by mentioning 'OpenID Connect' and 'standard OAuth scopes,' suggesting this is for authenticated LinkedIn operations. However, it doesn't provide explicit guidance on when to use this versus the 'get_profile' sibling tool or other alternatives.

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

Related 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/felipfr/linkedin-mcpserver'

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