Skip to main content
Glama
Sign In
linkedin-mcp

linkedin-mcp

by amankumar-2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Publish an image post on LinkedIn

create_image_post

Uploads one image from a local file or HTTPS URL and publishes it as a LinkedIn post with text, visibility, and optional alt text.

Instructions

Uploads one image (local file or https URL) and publishes it with the given text. Confirm the exact text and image 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_image_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesPost text. #hashtags are kept as hashtags; other formatting characters are posted literally.
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

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 covered. The description adds meaningful behavior beyond that: exactly one image per call, two accepted image sources, and a mandatory user-confirmation step before publishing. It does not disclose authentication requirements or what the call returns, keeping it below a 5.

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 with no filler. The capability statement comes first and the confirmation requirement follows, so the critical pre-call action is not buried.

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 publish action with five fully documented parameters and no output schema, the description covers what the tool does and the one procedural safeguard an agent needs. The remaining gap is that it never says what a successful call returns (post ID or URL), which matters for a non-idempotent write the agent may want to reference later.

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%, so text, alt_text, image_url, image_path, and visibility are already fully documented, and the enum default is spelled out. The description only restates the image-source choice (local file vs https URL) and adds nothing about alt_text or visibility semantics. Baseline 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?

"Uploads one image ... and publishes it with the given text" states a specific verb pair and the resource, and the "one image" constraint implicitly separates it from the text-only and link-post siblings. It stops short of explicitly naming those alternatives, so the differentiation is inferable rather than stated.

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 only guidance is a workflow prerequisite: "Confirm the exact text and image with the user first." That is useful, but there is no statement of when to pick this over create_text_post or create_link_post, nor any exclusion (e.g. multiple images, video). Usage is implied by the presence of an image.

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