Skip to main content
Glama

Get LinkedIn Profile

get_linkedin_profile
Read-onlyIdempotent

Reads one public LinkedIn person profile by its profile ID (the part after /in/ in the profile URL) and returns name, headline, location, summary, url, followers_count and connections_count; counts are rounded as LinkedIn shows them. It does not read company pages or private data, and does not search for people (use google_search to find a profile URL). Required: profile_id.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "get_linkedin_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYesPublic profile ID, the part after /in/ in a LinkedIn profile URL, e.g. "williamhgates" for https://www.linkedin.com/in/williamhgates/. Not a full URL or a company page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / profile_id / description
      Previous value: -"Public LinkedIn profile identifier from the profile URL."New value: +"Public profile ID, the part after /in/ in a LinkedIn profile URL, e.g. \"williamhgates\" for https://www.linkedin.com/in/williamhgates/. Not a full URL or a company page."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description still adds real behavioral context the annotations don't: the exact returned fields and the data-fidelity caveat that follower/connection counts are rounded as LinkedIn shows them. It omits rate limits, auth requirements, and failure modes (e.g. private or deleted profiles), which keeps this below a 5.

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?

One front-loaded sentence carries purpose, identifier, and return shape; a second sentence carries scope exclusions and the alternative; a short third states the requirement. No filler and no repetition of annotation-declared facts.

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 correctly compensates by listing the returned fields, and for a single-parameter read tool the input side is fully covered. Remaining gaps—error behavior for missing/private profiles and rate limiting—are modest but real for an openWorld scraper-style tool.

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 description coverage is 100% and the sole parameter is fully documented in-schema, including the 'williamhgates' example and the 'not a full URL or a company page' guard. The description restates the same guidance ('the part after /in/ in the profile URL', 'Required: profile_id') without adding syntax or format detail beyond it, so baseline 3 applies.

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?

Specific verb ('Reads') + specific resource ('one public LinkedIn person profile') + the identifier, plus an enumeration of the returned fields. It is clearly distinguishable from siblings like search_linkedin_jobs or x_profile, and it explicitly disclaims company pages and people search.

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

Usage Guidelines5/5

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

States the exclusions explicitly (no company pages, no private data, no people search) and names the alternative for the search case: 'use google_search to find a profile URL'. An agent knows both when to use it and where to go when it shouldn't.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources