Skip to main content
Glama
Hermoso

Hermoso

Official

Publish to LinkedIn

post_to_linkedin
Destructive

Publish a post to a connected personal LinkedIn profile — text plus an image, video, multi-image, link card, document, poll, or company @mentions. Posts publicly right away, so confirm the exact text first.

Instructions

Use this when the user wants to post to their personal LinkedIn profile. Publishing costs no credits. Publish a post to the user’s connected LinkedIn profile — text, and optionally an image (imageUrl), a VIDEO (videoUrl, with captionsSrt and a videoThumbnailUrl cover), a 2–20 image MULTI-IMAGE post (imageUrls), a LINK post with a real preview card (linkUrl + linkTitle / linkDescription / linkThumbnailUrl — LinkedIn never scrapes the page), a DOCUMENT post (documentUrl: a PDF / PPTX readers swipe through), and @mentions of companies (mentions). The image does NOT have to be something Hermoso generated: LinkedIn is served the bytes from us, so the URL must be Hermoso-hosted, and upload_file turns ANY file the user already has into exactly that. This PUBLISHES immediately and PUBLICLY — ALWAYS show the user the exact text and get an explicit yes BEFORE calling. Needs a connected LinkedIn account (Connectors > LinkedIn).

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

Input Schema

NameRequiredDescriptionDefault
hookNoWHAT ANGLE this post is built on, recorded only at publish time. post_performance ranks hooks on it (a winner needs 5 posts sharing ONE hook), so pass a list_hooks id (e.g. "direct_callout", "before_after") or reuse your own wording EXACTLY across a campaign. Omit it and this post never votes on which hook works.
pollNoa POLL as the post (question ≤140, 2-4 options ≤30); no media
textYesthe post text
brandNoWHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted.
titleNovideo title
ideaIdNoshort id of the content-plan idea this post came from
recipeNothe post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format
altTextNoimage alt text — a string for every image, or an array per slide
linkUrlNoa LINK post with a real preview card. Not with media.
subjectNoWHAT THIS POST IS ABOUT — product, feature, offer or theme (e.g. "winter coat", "free trial"). post_performance's second grouping axis: reuse the exact wording, as with hook.
imageUrlNoa Hermoso-hosted image URL to attach (≤12MB) — a Hermoso render, or ANY file of the user’s own put through upload_file first. An arbitrary external host is refused (we fetch the bytes ourselves); a URL, not a local file path; use upload_file for local files
mentionsNoTAG COMPANIES: write "@Name" in the text where each tag goes and list each company here — its vanity name (the part after linkedin.com/company/), its company page URL, or {organizationId, name}. Hermoso resolves it on LinkedIn and LinkedIn renders a real clickable mention; a company with no "@" spot in the text is refused rather than appended.
videoUrlNoa Hermoso-hosted video (a render, or the user’s footage via upload_file). LinkedIn processes it before publishing, which takes a minute; a URL, not a local file path; use upload_file for local files
imageUrlsNoa MULTI-IMAGE post: 2–20 Hermoso-hosted images in order, one post the reader swipes through (LinkedIn’s MultiImage API takes a member author on w_member_social). Images only.
linkTitleNothe card headline — LinkedIn never scrapes the page, so without it the card is unlabelled
reshareOfNoREPOST this post (link or urn); text optional, no media. Link cards come only from linkUrl
visibilityNodefault PUBLIC
captionsSrtNoSRT caption CONTENT for a videoUrl post (English only, attached during upload)
documentUrlNoa DOCUMENT post — a Hermoso-hosted PDF / PPTX / DOCX (upload_file first) that readers swipe through page by page in the feed; LinkedIn takes up to 100MB and 300 pages. One kind of media per post: not with an image, video, slides or linkUrl.
documentTitleNothe title shown on the document (defaults to the file name)
allowDuplicateNopost it even though an identical post was just made or attempted. Only pass this when the user genuinely wants the same thing posted twice, or when you have LOOKED at the account and confirmed a timed-out attempt did not land.
idempotencyKeyNoSAFE RETRIES — any stable string: a repeat of the SAME publish within 24h returns the ORIGINAL post id instead of posting again (an identical publish is also auto-recognised for 10 minutes). On a timeout or an ambiguous error, CALL AGAIN WITH THE SAME KEY: it reports the original post or publishes it once. It never posts twice.
linkDescriptionNolink card description; LinkedIn does not read the page, so set it here
linkThumbnailUrlNoHermoso-hosted image for the card
videoThumbnailUrlNocover image for a videoUrl post (Hermoso-hosted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.571
    • addedInput schema / properties / poll
      Added value: +{
      +  "description": "a POLL as the post (question ≤140, 2-4 options ≤30); no media",
      +  "properties": {
      +    "duration": {
      +      "enum": [
      +        "ONE_DAY",
      +        "THREE_DAYS",
      +        "SEVEN_DAYS",
      +        "FOURTEEN_DAYS"
      +      ],
      +      "type": "string"
      +    },
      +    "options": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "question": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "question",
      +    "options"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / reshareOf
      Added value: +{
      +  "description": "REPOST this post (link or urn); text optional, no media. Link cards come only from linkUrl",
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv0.1.525
    • changedInput schema / properties / imageUrl / description
      Previous value: -"a Hermoso-hosted image URL to attach (≤12MB) — a Hermoso render, or ANY file of the user’s own put through upload_file first. An arbitrary external host is refused (we fetch the bytes ourselves)."New value: +"a Hermoso-hosted image URL to attach (≤12MB) — a Hermoso render, or ANY file of the user’s own put through upload_file first. An arbitrary external host is refused (we fetch the bytes ourselves); a URL, not a local file path; use upload_file for local files"
    • changedInput schema / properties / videoUrl / description
      Previous value: -"a Hermoso-hosted video (a render, or the user’s footage via upload_file). LinkedIn processes it before publishing, which takes a minute."New value: +"a Hermoso-hosted video (a render, or the user’s footage via upload_file). LinkedIn processes it before publishing, which takes a minute; a URL, not a local file path; use upload_file for local files"
  3. Changed13 schema fields changedv0.1.465
    • addedInput schema / properties / altText
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  ],
      +  "description": "image alt text — a string for every image, or an array per slide"
      +}
    • addedInput schema / properties / captionsSrt
      Added value: +{
      +  "description": "SRT caption CONTENT for a videoUrl post (English only, attached during upload)",
      +  "type": "string"
      +}
    • addedInput schema / properties / documentTitle
      Added value: +{
      +  "description": "the title shown on the document (defaults to the file name)",
      +  "type": "string"
      +}
    • addedInput schema / properties / documentUrl
      Added value: +{
      +  "description": "a DOCUMENT post — a Hermoso-hosted PDF / PPTX / DOCX (upload_file first) that readers swipe through page by page in the feed; LinkedIn takes up to 100MB and 300 pages. One kind of media per post: not with an image, video, slides or linkUrl.",
      +  "type": "string"
      +}
    • changedInput schema / properties / imageUrls / description
      Previous value: -"A CAROUSEL IS NOT AVAILABLE ON A PERSONAL PROFILE — LinkedIn's organic multi-image post publishes from a COMPANY PAGE. Passing several here is refused by name rather than posting slide 1; use post_to_linkedin_page instead."New value: +"a MULTI-IMAGE post: 2–20 Hermoso-hosted images in order, one post the reader swipes through (LinkedIn’s MultiImage API takes a member author on w_member_social). Images only."
    • addedInput schema / properties / linkDescription
      Added value: +{
      +  "description": "link card description; LinkedIn does not read the page, so set it here",
      +  "type": "string"
      +}
    • addedInput schema / properties / linkThumbnailUrl
      Added value: +{
      +  "description": "Hermoso-hosted image for the card",
      +  "type": "string"
      +}
    • addedInput schema / properties / linkTitle
      Added value: +{
      +  "description": "the card headline — LinkedIn never scrapes the page, so without it the card is unlabelled",
      +  "type": "string"
      +}
    • addedInput schema / properties / linkUrl
      Added value: +{
      +  "description": "a LINK post with a real preview card. Not with media.",
      +  "type": "string"
      +}
    • addedInput schema / properties / mentions
      Added value: +{
      +  "description": "TAG COMPANIES: write \"@Name\" in the text where each tag goes and list each company here — its vanity name (the part after linkedin.com/company/), its company page URL, or {organizationId, name}. Hermoso resolves it on LinkedIn and LinkedIn renders a real clickable mention; a company with no \"@\" spot in the text is refused rather than appended.",
      +  "items": {},
      +  "type": "array"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "video title",
      +  "type": "string"
      +}
    • addedInput schema / properties / videoThumbnailUrl
      Added value: +{
      +  "description": "cover image for a videoUrl post (Hermoso-hosted)",
      +  "type": "string"
      +}
    • addedInput schema / properties / videoUrl
      Added value: +{
      +  "description": "a Hermoso-hosted video (a render, or the user’s footage via upload_file). LinkedIn processes it before publishing, which takes a minute.",
      +  "type": "string"
      +}
  4. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no brand, or two, is REFUSED and nothing is posted."New value: +"WHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted."
  5. Changed4 schema fields changedv0.1.320
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post belongs to — the id or exact name from list_brands (a workspace shared with you: its profile id). Use it whenever the account has more than one brand and you are not certain which one this connection is pinned to: it beats the pin for THIS CALL ONLY and changes nothing about the connection. A name that matches no brand, or two brands, is REFUSED and nothing is posted — never resolved to the pin, which is the account you were guarding against."New value: +"WHICH BRAND this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no brand, or two, is REFUSED and nothing is posted."
    • changedInput schema / properties / hook / description
      Previous value: -"WHAT ANGLE THIS POST IS BUILT ON — the single most valuable field here, and the only moment it can ever be recorded. post_performance groups on it to answer \"which hooks work\", and it needs 5 posts sharing ONE hook before it will call anything a winner, so REUSE THE SAME WORDING across a campaign instead of rephrasing it every time. Best of all, pass a hook id from list_hooks (e.g. \"direct_callout\", \"mid_problem\", \"before_after\") — those fold onto a stable key however they are spelled, so a whole brand accumulates evidence on one row. Your own wording is fine too; it just only groups when you repeat it exactly. Omitting it means this post can never vote on which hook works."New value: +"WHAT ANGLE this post is built on, recorded only at publish time. post_performance ranks hooks on it (a winner needs 5 posts sharing ONE hook), so pass a list_hooks id (e.g. \"direct_callout\", \"before_after\") or reuse your own wording EXACTLY across a campaign. Omit it and this post never votes on which hook works."
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"SAFE RETRIES. Publishing can take minutes (a video upload, a carousel of ten slides) and a transport can time out while the post SUCCEEDS — retrying blind is how the same thing gets posted twice. Pass any stable string here and a repeat of the SAME publish returns the ORIGINAL post id instead of posting again (24h). You do not have to: an identical publish is auto-recognised for 10 minutes anyway. If a call times out or errors ambiguously, CALL AGAIN WITH THE SAME KEY — that is the safe move, and it will either report the original post or publish it for the first time. It never posts twice."New value: +"SAFE RETRIES — any stable string: a repeat of the SAME publish within 24h returns the ORIGINAL post id instead of posting again (an identical publish is also auto-recognised for 10 minutes). On a timeout or an ambiguous error, CALL AGAIN WITH THE SAME KEY: it reports the original post or publishes it once. It never posts twice."
    • changedInput schema / properties / subject / description
      Previous value: -"WHAT THIS POST IS ABOUT — the product, feature, offer or theme (e.g. \"winter coat\", \"free trial\", \"founder story\"). The second grouping axis in post_performance. Same rule as hook: reuse the exact wording so posts about one subject land in one group."New value: +"WHAT THIS POST IS ABOUT — product, feature, offer or theme (e.g. \"winter coat\", \"free trial\"). post_performance's second grouping axis: reuse the exact wording, as with hook."
  6. Changed2 schema fields changedv0.1.281
    • addedInput schema / properties / ideaId
      Added value: +{
      +  "description": "short id of the content-plan idea this post came from",
      +  "type": "string"
      +}
    • addedInput schema / properties / recipe
      Added value: +{
      +  "description": "the post's FORMAT id, e.g. \"slideshow\" or \"imessage_chat\" — post_performance groups by it, so reuse one id per format",
      +  "type": "string"
      +}
  7. Changed1 schema field changedv0.1.251
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "WHICH BRAND this post belongs to — the id or exact name from list_brands (a workspace shared with you: its profile id). Use it whenever the account has more than one brand and you are not certain which one this connection is pinned to: it beats the pin for THIS CALL ONLY and changes nothing about the connection. A name that matches no brand, or two brands, is REFUSED and nothing is posted — never resolved to the pin, which is the account you were guarding against.",
      +  "type": "string"
      +}
  8. Addedv0.1.161

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that publishing is immediate and PUBLIC, mandates showing the user the exact text for an explicit yes, notes that publishing costs no credits, warns that video processing takes a minute, and explains refusal conditions (external-host URLs, unmatched @mention spots, ambiguous brand names). The idempotencyKey and allowDuplicate text explains exactly what happens on timeout or retry, which the annotations alone (idempotentHint=false) would not convey.

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?

Long but dense: the trigger, cost, and confirmation rule come first, followed by a compact catalogue of post types, then the hosting constraint and the publish-safety warning. Nearly every clause carries a distinct constraint; the only mild redundancy is the public/immediate warning echoed in the confirmation sentence.

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 25-parameter mutation tool with no output schema, the description covers the media matrix, mentions, documents, brand/hook/subject analytics fields, and retry semantics well. It stops short of describing what a successful call returns (post id/URL) or any rate limits, though the idempotency paragraph partially covers the id case.

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% and the schema's own field descriptions are already extensive, so the description largely restates what is in the schema (media variants, hosted-URL requirement, one-media-kind rule). It adds some connective value by grouping the mutually exclusive post types in one place, but no syntax or format detail beyond the schema, 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 and resource ("Publish a post to the user's connected LinkedIn profile") and scopes it to the personal profile, which separates it from post_to_linkedin_page. It then enumerates the concrete post shapes (text, image, video, multi-image, link, document, poll, repost) so an agent knows exactly what the tool produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ("Use this when the user wants to post to their personal LinkedIn profile") and names the prerequisite (a connected LinkedIn account via Connectors). It also routes to the right sibling for local files ("upload_file turns ANY file the user already has into exactly that") and lists the preconditions for each media variant.

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