LinkedIn MCP Server

update_partnerships

Update LinkedIn API partnership access settings after approval for special access to enable community, talent, sales, or marketing features.

Instructions

Update LinkedIn API partnership access settings when you get approved for special access

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_partnerships"
  }
}

Input Schema

Name	Required	Description
`communityManagement`	No	Enable Community Management API access for social features
`talentSolutions`	No	Enable Talent Solutions API access for job features
`salesSolutions`	No	Enable Sales Solutions API access for connection/messaging features
`marketingSolutions`	No	Enable Marketing Solutions API access for analytics features

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 15, 2025

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions an authorization condition but does not disclose potential side effects, idempotency, or what happens if the condition is not met. This is minimal 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, focused sentence that efficiently conveys the tool's purpose without extraneous words.

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?

Given that the tool modifies partnership access settings and has no output schema or annotations, the description lacks information about behavioral details (e.g., whether settings are additive, can be reversed, or any consequences). This is insufficient for a complete understanding.

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 provides complete descriptions for all four parameters (100% coverage), so the description adds no additional meaning. A 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 verb 'Update' and the resource 'LinkedIn API partnership access settings', and it distinguishes itself from sibling tools by focusing on partnership access, which is unique among the list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear usage context ('when you get approved for special access'), implying a prerequisite. While it does not explicitly state when not to use or mention alternatives, the context is sufficient given the lack of direct sibling overlaps.

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