Skip to main content
Glama

Iridium: LinkedIn MCP Server

schedule_manual_dm

Schedule Manual Dm

Schedule a direct message to someone you're already connected with. Use list_chats to find the chat_handle for a conversation. 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.

Args: chat_handle: chat_ handle from list_chats or list_replies text: Message text to send send_at: "now" to send immediately, else ISO-8601 e.g. "2026-06-11T09:00:00+00:00" message_type: "direct_message" (default) or "inmail"

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_manual_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
send_atNo
chat_handleYes
message_typeNodirect_message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers substantive behavior: an 8,000-character message cap, a 32-per-day DM ceiling covering new chats and replies together, and the two failure modes past that (429 refusal or a queued send deferred to the next day). It omits auth requirements and whether a scheduled send is cancellable or editable, but the rate-limit and refusal disclosure is well above baseline.

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 purpose and the key constraint are front-loaded, followed by a compact parameter block and then limits. The trailing OpenAPI scaffolding ('### Responses: 200 ... Content-Type: application/json') is auto-generated noise that adds nothing for an agent.

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 mutation tool with no annotations and no output schema, the description covers inputs, prerequisites, and throttling well. What it leaves out is the return shape — whether a scheduled send yields an identifier for cancel_scheduled or list_scheduled — which an agent needs to complete the schedule-then-manage loop.

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: all four parameters are documented with meaning beyond their names — chat_handle's provenance (list_chats or list_replies), text's 8,000-char limit, send_at's 'now' sentinel versus ISO-8601 with a worked example, and message_type's default and only alternate value. The one gap is that message_type's enum lives only in prose rather than the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Schedule a direct message') plus a scope constraint ('someone you're already connected with'), which narrows it meaningfully. It does not name or contrast with the obvious siblings schedule_dm_to_person or schedule_chat_reply, so the agent must infer the boundary from the connection qualifier alone.

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

Usage Guidelines3/5

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

Gives a useful precondition (target must already be a connection) and a concrete discovery path ('Use list_chats to find the chat_handle'), which is real when-to-use context. It stops short of saying when to prefer this over schedule_dm_to_person or schedule_chat_reply, and never states a when-not condition despite those siblings existing.

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