Skip to main content
Glama

Iridium: LinkedIn MCP Server

schedule_dm_to_person

Schedule Dm To Person

Send or schedule a direct message to a person you have already found. THIS SENDS.

ONE PERSON, THREE TOOLS - use them in this order:

  1. find_person WHO is this? A name (plus where they worked) returns a confirmed handle and proof. 1 search plus up to 2 profile reads.

  2. get_linkedin_profile TELL ME MORE. A handle returns the full profile and posts. Call it only when find_person's headline and proof are not enough.

  3. schedule_dm_to_person MESSAGE THEM. Pass the profile_handle from step 1. This tool takes a profile_handle, never a name: a name guesses between people who share it. If find_person's verdict is not confirmed, ask the user which person they mean first. Already in a conversation with them (see search_chats)? Use the chat_ handle with schedule_manual_dm instead; no lookup is needed.

If you already have a thread with this person the message goes into it. Otherwise it is a direct message to a connection, or a connection request with the text as its note. Several messages scheduled at once are spaced out so LinkedIn never sees a burst; the reply says so when a message is moved. 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. A connection-request note is limited to 300 characters and an InMail to 1,900.

Args: profile_handle: prof_ handle from find_person or get_linkedin_profile (required). text: the exact message to send. send_at: "now" to send immediately, or ISO-8601 with an offset. name: optional; shown in the queue. Read from the profile when omitted. message_type: optional override: connection_request, direct_message 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": {
      "text": "<text>"
    },
    "name": "schedule_dm_to_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
textYes
send_atNo
message_typeNo
profile_handleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the whole burden and does so: it signals that the tool actually sends ('THIS SENDS'), explains the three delivery modes (existing thread, DM to a connection, connection-request note), documents throttling (32 DMs/day, bursting is spaced out, 429 refusals, next-day queueing), and states per-type length limits (8,000 / 300 / 1,900).

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?

It is front-loaded with the send warning and the ordered tool chain before the detail, which is the right structure for a risky mutation. It is on the long side and the opening title echo ('Schedule Dm To Person') earns nothing, but the remaining sentences each carry operational information.

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 5-parameter mutation with no annotations and no output schema, the description covers delivery semantics, rate limits, and error behavior well. Its one gap is the return payload: it never says an identifier comes back that reschedule_send, cancel_scheduled, or list_scheduled would need, even though it mentions 'the reply says so when a message is moved.'

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 supply all meaning, and it defines every one of the five parameters: profile_handle's provenance ('prof_ handle from find_person or get_linkedin_profile'), text as the exact message, send_at's accepted values ('now' or ISO-8601 with offset), name's optionality and auto-fill behavior, and message_type's enumerated override values.

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 names the exact verb and resource ('Send or schedule a direct message to a person you have already found') and immediately disambiguates from its siblings by placing itself as step 3 in a three-tool chain and naming find_person, get_linkedin_profile, and schedule_manual_dm as different jobs.

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?

It gives explicit prerequisites (pass the profile_handle, never a name), a conditional branch (if find_person's verdict is not `confirmed`, ask the user first), and a named alternative with its triggering condition (existing conversation → schedule_manual_dm with the chat_ handle). Both when-to-use and when-not-to-use are covered.

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