Skip to main content
Glama

Iridium: LinkedIn MCP Server

schedule_chat_reply

Schedule Chat Reply

Send or schedule a message into an existing conversation. THIS SENDS.

It goes into a thread that already exists, so it creates no new connection and does not count against the daily connection limit, but it is a direct message and counts toward the daily DM cap. A message can be up to 8,000 characters. DMs are capped at 32 a day, new chats and replies together; past that, scheduling is refused (429) or a queued send waits until the next day. Call it only when the user has approved this specific message.

Args: chat_handle: chat_ handle from list_chats or search_chats. text: the exact message to send. send_at: "now" to send immediately, or ISO-8601 with an offset. Omit for immediate.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "chat_handle": "<chat_handle>",
      "text": "<text>"
    },
    "name": "schedule_chat_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
send_atNo
chat_handleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it flags the operation as a real send ("THIS SENDS"), states that it bypasses the connection limit but consumes the 32/day DM cap, gives the 8,000-character ceiling, and explains 429 refusal versus next-day queueing. These are exactly the side effects and rate constraints an agent needs before invoking a mutating tool.

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 critical constraint ("THIS SENDS") is front-loaded, and the body is dense with useful facts rather than filler. Minor waste comes from echoing the title as a first line and from the trailing Responses boilerplate, but the core is tight.

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 three-param mutating tool with no annotations and no output schema, the description covers limits, caps, failure modes, and approval prerequisites thoroughly. The only gap is return behavior: it notes a 200 success without saying what is returned (e.g., message id or scheduled-job reference) that an agent might need to confirm or later cancel via cancel_scheduled.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate and it does for all three params: chat_handle is sourced from list_chats or search_chats, text is "the exact message to send", and send_at accepts "now" or ISO-8601 with an offset, with omission meaning immediate. That is meaning well beyond the bare string types in the schema.

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 ("Send or schedule a message into an existing conversation") and immediately disambiguates scope: it targets a thread that already exists, creating no new connection. That cleanly separates it from siblings like schedule_dm_to_person and schedule_manual_dm, which do create new outreach.

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?

"Call it only when the user has approved this specific message" is an explicit precondition, and "send_at: 'now' ... Omit for immediate" gives clear operating guidance. It also warns that past the daily cap the call is refused with 429 or queued to the next day. It does not name a drafting sibling (draft_reply) to use when the message is not yet approved, so the routing guidance is clear but not exhaustive.

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.

Resources