Skip to main content
Glama

send_message

Send a LinkedIn message to a person using their profile URL or an existing conversation thread, with optional post-send conversation management.

Instructions

Allows you to send a message to a person (st.sendMessage action). Provide either personUrl or threadId (threadId replies into an existing conversation thread and takes precedence). Optionally pass manageConversation to archive, star, or mute the conversation right after the message is sent (chained st.manageConversation child, acting on the same thread). If this workflow is still running, do not retry this tool; retrying can send duplicate messages to the same person.

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
textYesThe message text, must be up to 1900 characters.
threadIdNoOptional conversation thread identifier to reply into, as returned by get_inbox. Provide this instead of personUrl to reply directly into a known thread.
personUrlNoLinkedIn URL of the person you want to send a message to (e.g., 'https://www.linkedin.com/in/john-doe'). Optional if threadId is provided.
manageConversationNoOptional. Manage the conversation right after the message is sent. Acts on the same thread, so no threadId is needed.
Behavior5/5

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

With no annotations, the description carries full disclosure responsibility. It thoroughly explains the async cloud-browser workflow, immediate status response, the need for polling via get_workflow_result, duplicate-message risks on retry, and the meaning of 'queued' vs 'outsideWorkingHours' pending reasons. This is exemplary behavioral transparency.

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 lengthy but justified given the tool's async complexity. It is front-loaded with the core purpose and well-structured into sequential guidance. However, the retry warning appears twice (first paragraph and later), creating minor redundancy that prevents a perfect score.

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?

The description covers all essential aspects: input alternatives, async workflow behavior, immediate response shape, result retrieval via get_workflow_result, retry prevention, and pendingReason interpretations. Given no annotations and no output schema, this is exceptionally complete for a complex tool.

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 already documents all parameters including personUrl vs threadId and manageConversation semantics. The description adds some nuance ('threadId takes precedence', chained child action) but largely restates schema info, so a baseline 3 is appropriate.

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 clearly states 'Allows you to send a message to a person (st.sendMessage action)', specifying the action and target. It also differentiates the two addressing modes (personUrl or threadId) and mentions the optional chained manageConversation, which is specific enough to distinguish from sibling tools.

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?

The description explicitly instructs when to use personUrl vs threadId, notes that threadId takes precedence, and explains the optional manageConversation. It provides strong guidance on when not to retry (while workflow is running) and directs users to call get_workflow_result for the final outcome, including interpretation of pendingReason states.

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