LinkedIn MCP Server

linkedin_add_publication

Add a publication (paper, article, or book) to your LinkedIn profile by specifying title, publisher, year, and optional URL and description.

Instructions

Add a publication (paper, article, book) 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": {
      "title": "<title>"
    },
    "name": "linkedin_add_publication"
  }
}

Input Schema

Name	Required	Description
`url`	No
`title`	Yes
`publisher`	No	Journal, conference or publisher.
`startYear`	No	Publication year, e.g. "2023".
`startMonth`	No	Publication month as a full name ("January") or number ("1").
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Aug 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, so the description adds no new behavioral context. It does not mention duplicate handling, authentication requirements, or what happens after a successful add. The phrase 'to the profile' is the only added context, but it 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, front-loaded sentence with no filler or redundancy. It efficiently conveys the tool's purpose.

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

Completeness3/5

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

For a simple write tool with no output schema, the description is minimally adequate. However, it does not mention that title is required or clarify the undocumented url/title/description fields, leaving some contextual gaps despite low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% (publisher, startYear, startMonth have descriptions; url, title, description do not). The description does not compensate by explaining these parameters or noting that title is required. It adds no parameter-specific semantics beyond the general term 'publication'.

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 uses a specific verb ('Add') and resource ('publication (paper, article, book)') with a clear target ('to the profile'). This clearly distinguishes it from sibling add_* tools like linkedin_add_award or linkedin_add_education.

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

Usage Guidelines3/5

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

The description implies its usage context—when you need to add a publication—but it provides no explicit guidance on when not to use it or how it differs from other add tools. With many sibling tools, explicit alternatives or exclusions would be helpful, but the current phrasing gives a reasonable hint.

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

Deploy Server