Skip to main content
Glama

LinkedIn profile

linkedin_profile
Read-only

LinkedIn Profile Lookup: one public LinkedIn profile by linkedin.com/in/ URL: name, followers, about text and photo link in the shared social schema. Experience, education and contact data are not returned. Bad input is free; not found or no match is not charged. Price: $0.02 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "url": "<url>"
    },
    "name": "linkedin_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe profile: a LinkedIn profile URL (linkedin.com/in/<name>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: it scopes the response (experience, education and contact data are not returned), discloses pricing ($0.02 per successful call), billing rules (bad input free, not-found uncharged) and the x402/USDC payment mechanism via _meta['x402/payment']. A determinism hint or response shape would have completed the picture, but this is well above the annotation baseline.

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 purpose and returned fields, then exclusions, then pricing and payment. Dense but every sentence carries operational information; the colon-chained clauses make it slightly harder to scan than separate sentences would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description's field enumeration and negative scoping (what is not returned) do the job the output schema would have done. Combined with billing and payment details, nothing an agent needs to invoke it successfully is missing.

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?

With 100% schema description coverage on a single parameter, the schema already carries the baseline, but the description reinforces the accepted URL form (linkedin.com/in/) and adds the otherwise invisible requirement to pass payment in _meta. This meaningfully reduces failed-call risk.

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?

States a specific verb and resource ('one public LinkedIn profile by linkedin.com/in/ URL') and enumerates the exact fields returned (name, followers, about text, photo link) in the shared social schema. The URL form (linkedin.com/in/) implicitly separates it from linkedin_company, but it never names a sibling explicitly.

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 implied by the input requirement: the caller must already hold a linkedin.com/in/ URL, which points to profile lookup rather than discovery tools like people_search or social_search. However, no explicit when-to-use or when-not statement is given, and the only conditional guidance is about billing, not tool selection.

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.