Skip to main content
Glama
maykonlong

LinkedIn MCP Server

by maykonlong

linkedin_add_skill

Add a skill to your LinkedIn profile by providing the skill name, updating your skills list for improved profile visibility and SEO.

Instructions

Adiciona uma nova habilidade ao perfil.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillYesNome da habilidade (ex: "Python", "TypeScript")
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'adds a new skill' but does not explain side effects (e.g., whether it appends to existing skills, requires authentication, or is irreversible).

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?

The description is a single, clear sentence with no wasted words. It is front-loaded and easy to parse, though it could be expanded with additional context without becoming wordy.

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?

For a simple one-parameter tool, the description is minimally sufficient but lacks details about the profile context, like whether this replaces or appends to the existing skill list. No output schema or annotations exist to fill gaps, but the tool's simplicity keeps this at an adequate level.

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?

The schema already covers the single parameter 'skill' with a clear description and example (100% coverage). The tool description does not add extra meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description clearly states the action (add) and the resource (a new skill to the profile), with a specific verb and object. It distinguishes itself from sibling tools by focusing on skills specifically, not experience or education.

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 is provided on when to use this tool versus alternatives. Sibling tools like linkedin_add_experience and linkedin_add_education exist, but the description does not mention them or clarify that this is the sole tool for adding skills.

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/maykonlong/Linkedin_mcp_server'

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