Skip to main content
Glama
maykonlong

LinkedIn MCP Server

by maykonlong

linkedin_add_experience

Add a new professional role to your LinkedIn profile with details like title, company, dates, location, and description. Automates profile experience updates.

Instructions

Adiciona uma nova experiência profissional ao perfil.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesCargo (ex: "Arquiteto de Software")
companyYesNome da empresa
endDateNoData de fim (formato MM/YYYY). Omita para cargo atual.
locationNoLocalização (opcional)
startDateYesData de início (formato MM/YYYY)
descriptionNoDescrição das atividades
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that a new experience is added, without mentioning permissions, side effects, reversibility, or what happens upon success/failure. This is inadequate for a mutation tool.

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

Conciseness5/5

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

The description is a single, concise sentence that effectively communicates the tool's purpose without unnecessary detail or repetition.

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?

For a mutation tool with no annotations and no output schema, the description is too sparse. It lacks operational context such as expected outcomes, constraints, or integration details. The schema covers parameters but not behavioral context.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The tool description adds no additional parameter meaning beyond what the schema already provides.

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 tool's function: adding a new professional experience to the profile. It uses a specific verb ('Adiciona') and resource ('experiência profissional'), which distinguishes it from sibling tools like linkedin_add_education and linkedin_add_skill.

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?

The description provides no guidance on when to use this tool versus alternatives such as linkedin_update_current_position. It does not mention prerequisites, exclusions, or scenarios where this tool should be preferred over others.

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