Skip to main content
Glama

Iridium: LinkedIn MCP Server

approve_reply_draft

Approve Reply Draft

Approve a reply draft and schedule it into the existing thread. THIS SENDS. It adds no new connection and does not count against the daily connection limit, but it is a direct message: it counts toward the cap of 32 DMs a day, and a message can be up to 8,000 characters.

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": {
      "handle": "<handle>"
    },
    "name": "approve_reply_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes
send_atNo
override_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 does substantial work: it flags 'THIS SENDS', clarifies it does not add a connection or consume the connection cap, but does consume the 32-DM/day cap, and gives an 8,000-character limit. What is missing is reversibility — whether the send can be cancelled via `cancel_scheduled` after approval — which matters greatly for an irreversible side effect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operational content is front-loaded and earns its place, but the heading repeats the tool name and the trailing '### Responses: **200**: Successful Response ... Content-Type: application/json' block is pure boilerplate that conveys nothing an agent needs.

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

Completeness3/5

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

For a sending mutation with no annotations and no output schema, the description covers rate-limit and length constraints well but leaves the parameters and post-send reversibility unexplained. It is adequate to know what the tool does but not fully sufficient to invoke it correctly with `override_text` or `send_at`.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and does not. `handle`, `send_at`, and `override_text` are never explained; in particular `override_text` silently replaces the drafted body and `send_at` controls deferral, both of which carry real consequences an agent cannot infer. The 8,000-character note is only loosely attributable to `override_text`.

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?

The description states a specific verb and resource: approving a reply draft and scheduling it into the existing thread. That distinguishes it from comment/content draft approvals by resource type, though it never explicitly contrasts itself with the sibling `approve_draft` or `approve_comment_draft`.

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?

Usage is implied by the resource name — you use this on a reply draft, not a comment or content draft — but there is no explicit when-to-use statement, no prerequisite (e.g. a draft must already exist via `draft_reply`), and no mention of when to prefer `schedule_chat_reply` or `reschedule_send` instead.

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