Skip to main content
Glama

create_post

Create a new LinkedIn post with text and optional media attachments, including images, videos, or documents. Supports posting to your profile or a company page.

Instructions

Creates a new LinkedIn post with optional media attachments (st.createPost action). If this workflow is still running, do not retry this tool; retrying can create duplicate posts.

Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.

A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesPost content, must be up to 3000 characters.
companyUrlNoLinkedIn company page URL. If specified, the post will be created on the company page (requires admin access).
attachmentsNoMedia attachments for the post. You can add up to 9 images, or 1 video, or 1 document. Cannot mix different attachment types.
Behavior5/5

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

With no annotations, the description fully discloses the queued execution, immediate pending response, duplicate risk on retry, pendingReason meanings, and long-polling behavior of get_workflow_result. This is rich, transparent behavioral disclosure beyond any structured metadata.

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?

The description is well-structured into paragraphs with a logical flow: purpose, retry warning, workflow mechanics, and pendingReason details. It is longer than typical but every sentence earns its place. Slightly dense but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the immediate response, async behavior, pending states (queued vs outsideWorkingHours), how to retrieve results, and retry precautions. Given the complexity and lack of output schema, this is complete and does not leave critical gaps.

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 baseline is 3. The description adds little beyond 'optional media attachments' – all parameter constraints (max 9 images, etc.) are already in the schema. No additional semantic value provided.

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 states 'Creates a new LinkedIn post with optional media attachments' which is a specific verb and resource, clearly distinguishing it from siblings like comment_on_post or react_to_post. It also mentions the st.createPost action, adding specificity.

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?

Provides clear context about the asynchronous workflow, including queuing, pending status, and the need to call get_workflow_result for final results. It explicitly warns against retrying while running, but does not mention alternative tools or when not to use this tool, so it falls short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zecloud/remote-mcp-linkedin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server