Skip to main content
Glama
Sign In
linkedin-mcp

linkedin-mcp

by amankumar-2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Publish a text post on LinkedIn

create_text_post

Publishes a text-only post to the signed-in member's LinkedIn feed after confirming the exact text with the user.

Instructions

Publishes a text-only post to the signed-in member's LinkedIn feed. Confirm the exact text with the user first.

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": {
      "text": "<text>"
    },
    "name": "create_text_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesPost text. #hashtags are kept as hashtags; other formatting characters are posted literally.
visibilityNoPUBLIC (anyone) or CONNECTIONS (your 1st-degree network).PUBLIC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, and destructive=false, so the safety profile is partly covered. The description still adds real context beyond them: the post goes to the signed-in member's own feed (account/identity scope) and requires user confirmation of the exact text before publishing. It does not warn that repeated calls create duplicate posts despite idempotentHint=false, which is the main remaining gap.

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?

Two short sentences, front-loaded with the action and scope, followed by the one operational instruction that matters. Nothing is redundant or padded.

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

Completeness4/5

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

For a 2-parameter, low-complexity publish tool with annotations and full schema coverage and no output schema, the description covers purpose, acting account, and the confirmation guardrail. The only meaningful omission is the duplicate-post consequence of non-idempotent retries.

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%: both `text` (maxLength 3000, hashtag handling) and `visibility` (PUBLIC/CONNECTIONS enum with default) are documented in the schema itself. The description adds only the "text-only" framing and no syntax, default, or visibility implications beyond the schema, so the baseline of 3 applies.

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?

"Publishes a text-only post to the signed-in member's LinkedIn feed" gives a specific verb (publishes), resource (post), and content constraint (text-only) plus the acting identity. The "text-only" qualifier implicitly separates it from image/link post variants, though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer it should call this when the content is plain text, and the description adds a precondition (confirm text with the user first). There is no explicit when-not guidance or reference to create_image_post/create_link_post for other content types, so routing between siblings is left to inference.

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

Deploy Server

Other Tools