Skip to main content
Glama
joaovaleri

linkedin-mcp

by joaovaleri

linkedin_add_organization

Add an organization membership to your LinkedIn profile with details like name, position, dates, and description.

Instructions

Add an organization membership to the LinkedIn profile

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
endYearNo
endMonthNo
positionNo
isCurrentNo
startYearNo
startMonthNo
descriptionNo
Behavior2/5

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

The description lacks behavioral disclosure. With no annotations, it should describe side effects like whether it appends or overwrites, if authentication is required, or any rate limits. The current text gives no such information.

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

Conciseness2/5

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

The description is extremely short (9 words) but lacks structure and value. It could be expanded with a more informative structure without being verbose.

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

Completeness1/5

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

Given 8 parameters, no annotations, and many similar sibling tools, the description is wholly incomplete. It doesn't clarify what an 'organization membership' is on LinkedIn, how it differs from experience or volunteer, or what date formats to use.

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%, and the description does not explain any of the 8 parameters (e.g., date formats, how 'position' relates, or the meaning of 'isCurrent'). The user gets no guidance beyond parameter names.

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?

The description clearly states the verb 'Add' and the resource 'organization membership', specifying it modifies the LinkedIn profile. However, it doesn't differentiate from very similar sibling tools like 'linkedin_add_volunteer' or 'linkedin_add_experience', which could also involve organizations.

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. For example, there is no mention that this tool is for adding a separate organization section (e.g., non-profit board) versus adding a work experience entry under an organization.

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