LinkedIn MCP Server

linkedin_add_volunteer_experience

Add volunteer experience to your LinkedIn profile, specifying organization, role, cause, dates, and description.

Instructions

Add volunteer experience to the profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organization": "<organization>",
      "role": "<role>"
    },
    "name": "linkedin_add_volunteer_experience"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	Your role.
`cause`	No
`current`	No
`endYear`	No	End year, e.g. "2023".
`endMonth`	No	End month as a full name ("January") or number ("1").
`startYear`	No	Start year, e.g. "2023".
`startMonth`	No	Start month as a full name ("January") or number ("1").
`description`	No
`organization`	Yes	Organisation name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Aug 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already indicate this is a mutation (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description's 'Add' aligns with annotations but adds no additional behavioral context, such as whether the new entry is appended, if duplicates are possible, or if any related profile data is affected. With no extra context beyond annotations, transparency is minimal.

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: 'Add volunteer experience to the profile.' It is front-loaded with the verb and target, with zero waste. Every word contributes to the purpose.

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?

This is a write operation with 9 parameters and no output schema. The description does not explain the expected return value, how the tool affects existing profile data, or any prerequisites. It is minimally functional but fails to provide contextual completeness for an agent to anticipate behavior beyond the action itself.

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 67% (6 of 9 parameters described). The description itself does not mention any parameters or clarify the undocumented ones like 'current' or 'cause'. Since coverage is moderate and the description adds no value, the 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 'Add volunteer experience to the profile' uses a specific verb ('Add'), identifies the resource ('volunteer experience'), and the target ('profile'). The name itself distinguishes it from sibling add_* tools (e.g., add_experience, add_project) by the resource type, so purpose is clear.

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 vs alternatives such as add_experience, nor any prerequisites or context about volunteer experience vs other profile sections. There are no exclusions or alternative suggestions, leaving the agent without decision criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server