Skip to main content
Glama

LinkedIn Profile Info

linkedin_profile_info

[Acquire · 5 credits] Fetch a LinkedIn person profile (headline, current role, work history, education, location). Costs 5 credits per call. Results are upserted into people (structured fields) and linkedin_profiles (so profile-brief renders) — same enrichment side-effect as the other linkedin_profile_* tools.

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": {
      "linkedin_url": "<linkedin_url>"
    },
    "name": "linkedin_profile_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoBypass the cache and fetch a fresh copy from LinkedIn (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
linkedin_urlYesLinkedIn profile URL (e.g. https://www.linkedin.com/in/username)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and openWorldHint=true, and the description usefully explains why: results are upserted into `people` and `linkedin_profiles`, plus it discloses the 5-credit cost and that cached hits are free. It stops short of covering failure modes, auth/permission requirements, or rate limits, so it is strong but not exhaustive.

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?

Front-loaded with the cost tag and the core action, then the side effects, which is the right order for an agent deciding whether to spend credits. Minor redundancy: 'Costs 5 credits per call' repeats the '[Acquire · 5 credits]' tag.

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 does the necessary work by naming the fields returned and the write side effects, and the schema carries refresh/cache details. It could say more about what the cached payload looks like or what happens on fetch failure, but nothing essential for correct invocation is missing.

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%, so both linkedin_url and refresh (including its 'costs 5 credits' and cache semantics) are already documented in the schema. The description adds little parameter-level meaning beyond restating the per-call credit cost, so the 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 (Fetch) plus specific resource (LinkedIn person profile) with an enumerated field list (headline, current role, work history, education, location). The word 'person' plus the profile-field list clearly separates it from linkedin_company_info, and the closing clause groups it with the linkedin_profile_* activity tools.

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?

Usage is only implied: the agent can infer this is the tool for full profile data rather than posts/comments, and the refresh parameter explains cache vs fresh fetch. But there is no explicit when-to-use or when-not guidance, and nothing tells the agent to first resolve a URL via linkedin_people_search even though linkedin_url is required.

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