Skip to main content
Glama

LinkedIn: Create post

linkedin_create_post
Destructive

Publish a LinkedIn post from the user's own account, optionally on a managed company page using post_as from linkedin_list_managed_company_pages. This is a public side effect; use only after the user has clearly approved the final content and target identity.

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_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesLinkedIn Classic mentions belong in text: @ followed by the resolved person's Classic ACo... ID or the company's numeric ID (for example @1441). Resolve people with linkedin_get_profile_from_url/linkedin_resolve_person and companies with linkedin_resolve_company/linkedin_search_companies; disambiguate every target before publishing. Never use a display name, profile URL, company slug, URN, Sales Navigator or Recruiter ID as a mention. Example after resolving both targets: 'Thanks @ACo_RESOLVED_MEMBER for working with @1441.' The API replaces each token with the target's name and mention metadata; no separate mentions field is needed. Approve the final text and mentioned identities before the write; never retry an ambiguous write automatically.
post_asNoOptional numeric CompanyPage.id from linkedin_list_managed_company_pages for the SAME account_id. Choose the page by name from that list; never use mailbox_id, inbox_id, a company URL/slug, name, URN or person ID. Omit to act as the connected person. Requires the company product enabled during account_connect and current page admin rights; company search alone does not prove access. Never omit this field as a fallback after a company action fails.
can_readNo
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
can_commentNo
quoted_post_idNoExact provider post ID to quote, returned by post search/list/get. Never pass post text or a URL. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / post_as / description
      Previous value: -"Exact managed page/company identity returned by linkedin_list_managed_pages; omit to post as the connected person. Never pass a company name or URL."New value: +"Optional numeric CompanyPage.id from linkedin_list_managed_company_pages for the SAME account_id. Choose the page by name from that list; never use mailbox_id, inbox_id, a company URL/slug, name, URN or person ID. Omit to act as the connected person. Requires the company product enabled during account_connect and current page admin rights; company search alone does not prove access. Never omit this field as a fallback after a company action fails."
    • addedInput schema / properties / post_as / pattern
      Added value: +"^\\d+$"
  2. Changed1 schema field changed
    • addedInput schema / properties / text / description
      Added value: +"LinkedIn Classic mentions belong in text: @ followed by the resolved person's Classic ACo... ID or the company's numeric ID (for example @1441). Resolve people with linkedin_get_profile_from_url/linkedin_resolve_person and companies with linkedin_resolve_company/linkedin_search_companies; disambiguate every target before publishing. Never use a display name, profile URL, company slug, URN, Sales Navigator or Recruiter ID as a mention. Example after resolving both targets: 'Thanks @ACo_RESOLVED_MEMBER for working with @1441.' The API replaces each token with the target's name and mention metadata; no separate mentions field is needed. Approve the final text and mentioned identities before the write; never retry an ambiguous write automatically."
  3. Changed1 schema field changed
    • changedInput schema / properties / quoted_post_id / description
      Previous value: -"Exact provider post ID to quote, returned by post search/list/get. Never pass post text or a URL. Post ID: Exact provider/Unipile post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it."New value: +"Exact provider post ID to quote, returned by post search/list/get. Never pass post text or a URL. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it."
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the safety bar is partly covered; the description adds the important framing that this is a *public* side effect requiring approved content and identity. The schema further warns never to retry an ambiguous write. It doesn't discuss rate limits or the shape of a successful response, which is acceptable given no output schema.

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, both load-bearing, with the publish/scope statement front-loaded and the approval gate second. Nothing redundant.

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 non-idempotent public write with no output schema, the description covers the essentials: identity selection, scope, and the human-approval precondition. The remaining gap is the un-explained audience fields (can_read/can_comment), which an agent must infer from enum values.

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 67%; the description reinforces post_as (must come from linkedin_list_managed_company_pages for the same account_id, requires page admin rights) but that content largely duplicates the schema text. The audience parameters can_read and can_comment have no description in either the schema or the tool description, so meaning is left to the enum values alone.

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 and resource ("Publish a LinkedIn post") plus the two identity modes: the user's own account by default, or a managed company page via post_as. An agent can distinguish this from linkedin_comment_on_post and from facebook_create_post without inspecting either schema.

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?

Gives an explicit gating condition — use only after the user has clearly approved final content and target identity — which is the key when-to-use rule for a publish action. It does not name competing tools (e.g. comment vs post) explicitly, so it stops short of full when-not/alternatives guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.