Skip to main content
Glama

LinkMCP: hosted LinkedIn MCP server

by io.linkmcp
OverviewDiscussionsAdmin

Create Post

linkedin_create_post
Destructive

Create a LinkedIn post. Supports text with line breaks, image attachments (via public URLs), @mentions, link preview cards, and reposting existing posts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesPost content (max 3000 characters). Use \n for line breaks. Use {{0}}, {{1}} etc. to insert mentions from the mentions array.
repostNoOptional social_id of an existing LinkedIn post to share/repost. For a simple repost without commentary, text can be empty.
as_pageNoOptional. Publish the post as a LinkedIn company page that you administer: the page_id from linkedin_list_company_pages. The post is public under the page name, not under your name. Omit it to post as yourself.
mentionsNoOptional mentions array. Reference in text as {{0}}, {{1}} etc.
image_urlsNoOptional array of publicly accessible image URLs (JPEG, PNG, GIF, max 5MB each, max 20). The server will fetch and attach them to the post.
content_checkNoControls LLM content artifact detection (default: "strict"). "strict" rejects text containing Unicode dashes (— – −) and other LLM artifacts. "autofix" automatically replaces em dashes with short dashes. "disabled" skips all content checks.
external_linkNoOptional URL for a link preview card. Must also appear in the post text. If a preview is not available, the link stays in the text and the answer has a note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / external_link / description
      Previous value: -"Optional URL for a link preview card. Must also appear in the post text."New value: +"Optional URL for a link preview card. Must also appear in the post text. If a preview is not available, the link stays in the text and the answer has a note."
  2. Changed1 schema field changed
    • addedInput schema / properties / as_page
      Added value: +{
+  "description": "Optional. Publish the post as a LinkedIn company page that you administer: the page_id from linkedin_list_company_pages. The post is public under the page name, not under your name. Omit it to post as yourself.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description itself only restates capabilities and does not add behavioral context such as irreversibility of publishing, visibility/audience consequences, or rate limits; the richer behavioral notes (content_check strictness, server-side image fetching, link-preview fallback) live in the schema rather than the description.

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?

A single front-loaded sentence naming the action first, followed by a compact capability list. No filler, no redundancy, and the most important information (create a post) leads.

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 7-parameter mutation tool with no output schema, the description covers the main content modes but omits what the call returns (e.g. post ID/URL) and any failure modes or permission requirements. Annotations plus the fully documented schema carry most of the load, leaving this adequate but not complete.

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 the schema already documents every parameter in detail (character limits, mention placeholder syntax, page posting, content_check modes). The description adds nothing beyond what the schema provides, 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?

States a specific verb+resource ('Create a LinkedIn post') and then enumerates the supported content modes (text, images, mentions, link cards, reposts). This clearly separates it from siblings like linkedin_comment_on_post and linkedin_react_to_post, which act on existing posts rather than producing new ones.

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: the capability list hints at when to reach for this tool (multi-modal publishing, reposting), and the as_page parameter notes 'Omit it to post as yourself.' There is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g. needing a connection/page admin), and no named alternatives.

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

All LinkMCP: hosted LinkedIn MCP server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources