Skip to main content
Glama
alexanderskorokhodov

remote-mcp-linkedin

LinkedIn Profile Dossier

linkedin_profile_dossier
Read-only

Build a structured dossier from visible LinkedIn profile sections to analyze key profile data.

Instructions

Build a deterministic structured dossier from visible profile sections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameNo
profile_urlNo
include_postsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations indicate readOnlyHint and openWorldHint. Description adds 'deterministic structured dossier' which implies consistency beyond what annotations provide. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded, but too brief. Leaves out critical parameter explanations and usage context. Appropriate length but incomplete.

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

Completeness2/5

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

Three parameters with no schema coverage, one sibling tool. Description lacks details on dossier contents, parameter selection logic, and output structure despite having an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but description adds no meaning to parameters. Does not explain the purpose of 'username', 'profile_url', or 'include_posts'.

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?

Clearly states it builds a structured dossier from visible profile sections. Specific verb and resource, but does not explicitly differentiate from sibling 'linkedin_profile_get'.

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?

No guidance on when to use this tool vs alternatives. The description does not mention when to use it over 'linkedin_profile_get' or any context for selection.

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/alexanderskorokhodov/remote-mcp-linkedin'

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