Skip to main content
Glama
joaovaleri

linkedin-mcp

by joaovaleri

linkedin_add_experience

Add a work experience entry to a LinkedIn profile by specifying job title, company, dates, and description. Automates profile updates for current or past roles.

Instructions

Add a work experience entry to the LinkedIn profile

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesJob title
companyYesCompany name
endYearNoEnd year (omit if current)
endMonthNoEnd month (omit if current)
locationNoJob location
isCurrentNoIs this the current job?
startYearYesStart year (e.g. '2022')
startMonthYesStart month (e.g. 'Janeiro')
descriptionNoJob description
Behavior2/5

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

No annotations provided. The description only says 'add' with no details on side effects, permissions, rate limits, or whether it overwrites existing entries. For a mutation tool, this is insufficient.

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?

Single sentence, no unnecessary words. While extremely brief, it is concisely structured. Could be slightly improved with additional context.

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?

With 9 parameters and no output schema, the description omits crucial context like return value, error handling, and prerequisites (e.g., must be logged in). Incomplete for a complex tool.

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% with each parameter having a description. The tool description adds nothing beyond the schema, so baseline score 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 tool adds a work experience entry to the LinkedIn profile, with a specific verb ('add') and resource ('work experience entry'). It is distinct from sibling tools like linkedin_add_education or 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?

No guidance on when to use this tool versus alternatives, such as updating existing experience or adding other profile sections. No prerequisites mentioned (e.g., login via linkedin_login).

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

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