Skip to main content
Glama
Sign In
linkedin-mcp

linkedin-mcp

by amankumar-2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Preview a LinkedIn post

preview_post
Read-only

Show exactly what a LinkedIn text, link, or image post will contain before publishing, without uploading images or creating the post.

Instructions

Shows exactly what would be sent to LinkedIn for a text, link or image post, without publishing anything or uploading images. Use this to show the user the post before creating it.

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": "preview_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoLink to share.
kindNotext
textYesPost text. #hashtags are kept as hashtags; other formatting characters are posted literally.
titleNoTitle shown on the link card (LinkedIn does not fetch it from the page).
alt_textNoAlt text for screen readers.
image_urlNohttps:// URL of a PNG, JPEG or GIF to download and attach.
image_pathNoLocal path to a PNG, JPEG or GIF (max 8 MB).
visibilityNoPUBLIC (anyone) or CONNECTIONS (your 1st-degree network).PUBLIC
descriptionNoOptional description shown on the link card.
thumbnail_pathNoOptional local PNG/JPEG/GIF to use as the link card image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description builds on that by disclosing two non-obvious behaviors: nothing is published and images are not uploaded/downloaded during preview. It stops short of describing the shape of the preview output or how invalid image paths are reported.

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 sentences with the key non-mutating guarantee front-loaded, and the usage instruction following. No redundant restatement of the title or schema.

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 10-parameter, schema-rich tool with no output schema, the description covers the essential safety profile and the purpose. A note on what the preview actually returns (format of the rendered post) would close the remaining gap.

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 coverage is 90% and the schema documents text/link/image fields thoroughly, so the description's mention of 'text, link or image post' merely mirrors the kind enum. It adds no format or constraint detail beyond what the schema supplies, so the baseline 3 applies.

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?

Names a specific verb (shows/preview) and resource (post for text, link or image), and the 'without publishing anything or uploading images' clause sharply separates it from the create_* siblings that otherwise look identical.

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?

'Use this to show the user the post before creating it' gives a clear trigger and implies the preview-then-create workflow. It does not explicitly name create_text_post/create_link_post/create_image_post as the follow-up alternatives, but the conditional guidance is unambiguous.

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