Skip to main content
Glama
felipfr

LinkedIn MCP Server

by felipfr

get_connections

Retrieve your complete LinkedIn connections list. Access your network data for analysis and management.

Instructions

Retrieve your complete LinkedIn connections list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Actual implementation of get_connections. Makes a GET request to '/connections?start=0&count=100' and returns a typed ConnectionsResult.
    public async getConnections(): Promise<ConnectionsResult> {
      return this.makeRequest<ConnectionsResult>('get', '/connections?start=0&count=100')
    }
  • src/server.ts:177-192 (registration)
    Registers the 'get-connections' tool on the MCP server with empty params schema and a handler that calls clientService.getConnections().
    // Get Connections Tool
    this.server.tool(
      'get-connections',
      'Retrieve the current user connections',
      linkedinApiSchemas.emptyParams,
      async () => {
        this.logger.info('Retrieving User Connections')
        try {
          const connections = await this.clientService.getConnections()
          return this.createResourceResponse(connections)
        } catch (error) {
          this.logger.error('User Connections Retrieval Failed', error)
          throw error
        }
      }
    )
  • Defines emptyParams schema (empty object) used by get-connections tool since it requires no input parameters.
    export const linkedinApiSchemas = {
      /**
       * Empty parameters schema for endpoints without required parameters
       */
      emptyParams: {},
  • TypeScript type definition for ConnectionsResult returned by getConnections(). Contains connections array with id, firstName, lastName, headline, profilePicture and paging info (count, start, total).
    export interface ConnectionsResult {
      connections: {
        id: string
        firstName: string
        lastName: string
        headline?: string
        profilePicture?: ProfilePicture
      }[]
      paging: {
        count: number
        start: number
        total: number
      }
    }
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 for behavioral disclosure. It only states a read operation ('retrieve') but does not mention authentication requirements, rate limits, or any side effects. This is insufficient for a tool with no annotations.

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, front-loaded sentence that efficiently conveys the tool's purpose without any extraneous words. Every part earns its place.

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?

For a zero-parameter tool with no output schema, the description is minimally adequate but lacks details about return format, pagination, or any error conditions. It does not specify that authentication is required, which could lead to incorrect usage. However, the tool's simplicity partly compensates.

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?

The input schema has no parameters, so schema description coverage is 100%. The description adds no parameter information, which is acceptable. Baseline for high coverage is 3, and the description does not degrade or improve it.

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 tool retrieves the user's complete LinkedIn connections list. It uses a specific verb ('retrieve') and resource ('connections list'), which distinguishes it from sibling tools like 'get_connection_requests' that deal with pending requests.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'get_connection_requests', 'get_profile', or search tools. It does not specify prerequisites or context, leaving the agent to infer.

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

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