Skip to main content
Glama

LinkedIn: Get profile

linkedin_get_profile
Read-onlyIdempotent

Get a LinkedIn person's full profile from a LinkedIn provider user ID, public identifier, or linkedin.com/in/... URL using the user's own account. Use it to retrieve a profile and resolve its stable ID from a supplied URL. The result contains the stable user id needed by linkedin_start_conversation and linkedin_send_invitation. Optional sections can retrieve experience, skills, interests and other profile details.

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": {
      "user_id_or_url": "<user_id_or_url>"
    },
    "name": "linkedin_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNo
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
with_sectionsNoClassic-only optional sections such as linkedin_experience, linkedin_skills or preview variants.
user_id_or_urlYesLinkedIn user ID (for example ACo...), public identifier, or full linkedin.com/in/... profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description adds genuinely new facts — retrieval uses the user's own account, and optional sections must be requested explicitly — but says nothing about rate limits, per-variant behavior, or the cost/preview tradeoff implied by the section enum.

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?

Four compact sentences, front-loaded with the input forms and followed by the downstream purpose and the optional sections. No filler, though the URL-resolving clause slightly duplicates the opening statement.

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?

With no output schema, the description does some of the return-value work by naming the stable user id and the retrievable sections. It still leaves gaps that matter for a four-parameter tool: the variant parameter is unaddressed and the preview-vs-full section distinction is only hinted at.

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 75%, so the schema already documents user_id_or_url, account_id and with_sections well. The description restates the accepted identifier formats and the section categories without adding detail, and it never mentions the 'variant' parameter (linkedin_classic / sales_navigator / recruiter), which has no schema description at all.

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 names a specific verb and resource ('Get a LinkedIn person's full profile') and lists the three accepted input forms (provider user ID, public identifier, profile URL). It does not, however, distinguish itself from close siblings such as linkedin_get_profile_from_url, linkedin_resolve_person, or linkedin_visit_profile, which the accepted-URL input form overlaps with.

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?

It gives a downstream-driven rationale ('the stable user id needed by linkedin_start_conversation and linkedin_send_invitation'), which is useful context for when to call it. But it never states when to prefer linkedin_get_profile_from_url or linkedin_resolve_person instead, leaving a real ambiguity unresolved.

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.