Skip to main content
Glama

HeyReagent LinkedIn MCP

by io.github.linglistack
OverviewDiscussionsAdmin

Publish a post

create_post
Destructive

[Ids in: repostOf (optional): post link or post social id; jobPostingId (optional): job id, from list_job_postings → jobPostings[].id. Ids out: postId: post id.] Publish ONE post on your own LinkedIn profile, now (max 3000 characters). Optional: images, a video or a document, a repost of an existing post (with or without your own text), mentions, a link preview card, a job posting card, posting as a company page you administer, and limiting who sees it. It is public as soon as it is sent and this tool cannot edit or delete it afterwards — show the user the exact text and get a yes first. Counts against the account's daily post allowance (5 a day).

Input Schema

NameRequiredDescriptionDefault
linkNoA link to show as a preview card. It should also appear in the text; otherwise LinkedIn adds it at the end.
textNoThe post text, exactly as it should appear. May be empty only for a plain repost.
audienceNoLimit who sees the post (company-page posts). Each list holds LinkedIn ids from lookup_search_ids (types LANGUAGE, POST_JOB_FUNCTION, SCHOOL, SENIORITY, INDUSTRY, REGION, LOCATION); headcount is company-size ranges such as { min: 51, max: 200 }.
mentionsNoPeople or companies to mention. Put {{0}}, {{1}}, … in the text where each one goes (its position in this list).
repostOfNoURL of an existing LinkedIn post to repost. With empty text it is a plain repost; with text, a repost with your thoughts.
connectionIdNoWhich of your LinkedIn accounts to act from (its id from list_linkedin_accounts). Omit to use your first live one.
jobPostingIdNoId of one of your job postings to show as a card (from list_job_postings).
asOrganizationNoAct as a company page you administer instead of yourself: that page's numeric id.
attachmentUrlsNoImages, one video or one document to attach. Public https links; each file up to 10 MB, 20 MB in total.
videoThumbnailUrlNoCover image for an attached video (a public https link).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the post is public the moment it is sent, that the tool can never edit or delete it afterwards, that the user must approve the exact text, and that a 5-per-day account allowance applies. These are the exact side effects and limits an agent needs for an irreversible write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and mostly front-loaded, with the public/irreversible warning placed before the optional-feature enumeration. The bracketed '[Ids in: …]' preamble is mechanically formatted and slightly awkward, but no sentence is wasted.

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, nested-object mutation with no output schema, the description covers safety, limits, id provenance, and feature scope. It does not restate return values, which is fine given postId is named, though it could say more about failure modes when the daily cap is hit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value: it labels repostOf and jobPostingId as inbound ids with their source tools (list_job_postings) and returns postId as the output id, and it explains empty text being valid only for a plain repost.

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 ONE post on your own LinkedIn profile, now' — with scope (single post, 3000 char cap) that immediately separates it from comment_on_post, react_to_post, and get_post in the sibling list.

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 clear context for invoking it (public immediately, requires user confirmation, consumes one of 5 daily posts) and enumerates the supported variations. It stops short of explicitly naming an alternative tool to use for the adjacent cases (e.g. editing or deleting an existing post, which no sibling offers).

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

All HeyReagent LinkedIn MCP 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