linkedin-mcp-server

linkedin_create_image_post

Create LinkedIn posts with exactly one image using a local file, public URL, search query, or AI-generated photorealistic visual.

Instructions

Create a LinkedIn post with exactly one image. Supports local file path, public image URL, internet image search query, or AI image generation prompt tuned for photorealistic results.

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

Input Schema

Name	Required	Description
`text`	Yes	Commentary for the image post (hashtags will be appended at the end)
`altText`	No	Optional accessibility text for the image
`hashtags`	No	Optional hashtags. If omitted, hashtags are auto-generated and appended at the end of the post.
`imageUrl`	No	Public image URL
`imagePath`	No	Local image path (.jpg, .jpeg, .png, .gif, .webp)
`visibility`	No	Post visibility: PUBLIC (default), CONNECTIONS, or LOGGED_IN
`imageSearchQuery`	No	Search query to fetch a related internet image. Use this instead of imagePath/imageUrl.
`imageGenerationPrompt`	No	Prompt to generate a photorealistic AI image (text overlays/logos are discouraged by default). Use this instead of imagePath/imageUrl/imageSearchQuery.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description handles disclosure by noting that hashtags are appended, AI generation is photorealistic, and text overlays/logos are discouraged. It does not mention permissions, publication timing, or error behavior if multiple image sources are supplied, which would improve transparency.

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 two sentences: the first states the primary action and constraint ('exactly one image'), the second lists the supported image sources. It is front-loaded and contains no filler.

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 an 8-parameter create tool with full schema coverage, the description provides a solid overview of the image modes and the posting action. It does not explain behavior when multiple image sources are provided or specify output, but these are not essential for initial invocation.

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 100% with detailed descriptions for every parameter, so the baseline is 3. The description's summary of the four image modes adds minor value by confirming the alternatives, but the schema already conveys a mutual exclusivity via 'Use this instead'.

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 tool creates a LinkedIn post with exactly one image, and explicitly lists the four supported image sources (local file, URL, search query, generation prompt). This distinguishes it from sibling tools like linkedin_create_post (text-only) and linkedin_create_article_post (articles).

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 implies use for single-image posts and provides explicit guidance on image source options, with parameter-level 'Use this instead' instructions. However, it does not explicitly name alternative tools or state when not to use this tool, leaving some ambiguity.

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

Deploy Server