Skip to main content
Glama

Open a reply for you to send

reply_open

Copies an approved reply to the clipboard and opens its LinkedIn thread for manual paste and send, or opens messaging with the recipient named if the thread link is unknown; nothing is sent.

Instructions

Puts an approved reply on the clipboard and opens the thread in the browser, so you press Cmd+V, read it, and press Enter. It sends nothing: no browser automation and no API call. When the thread link is unknown it opens LinkedIn messaging and names who to search for. Stops while the halt file exists. With LINKEN_DRY_RUN=1 it copies and opens nothing.

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": {
      "thread": "<thread>",
      "text": "<text>"
    },
    "name": "reply_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reply, as plain text, after the member approved it.
threadYesThe thread id, as inbox_next returns it (the export's CONVERSATION ID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.5/5.0
Behavior5/5

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

It goes well beyond what the annotations cover. Annotations only show readOnlyHint=false and openWorldHint=true, but the description discloses the clipboard and browser side effects, that the halt file stops execution, and that LINKEN_DRY_RUN=1 changes behavior. It also explains the fallback when the thread link is unknown, which is exactly the operational context an agent needs.

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

Conciseness5/5

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

The main effect is stated first, then the safety clarification, then the edge cases in short clauses. Every sentence adds distinct information, and there is no filler.

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?

For a tool with environment-variable behavior, a halt mechanism, and a fallback path, the description covers all the operational branches an agent must anticipate. No output schema is needed because the tool has no meaningful return value beyond opening the browser and populating the clipboard.

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 coverage is 100%, and the schema already defines the thread id and the reply text, so the description adds little extra meaning for both parameters. The fallback note about the thread link partly references the thread parameter but gives no format or validation details beyond that. The baseline of 3 is appropriate because the schema does the heavy lifting.

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 concrete verb and two concrete effects: "Puts an approved reply on the clipboard and opens the thread in the browser." This clearly separates it from sibling write tools like comment_create or post_publish, since it explicitly says the human performs the send.

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?

The description makes the usage context explicit: it runs after the member has approved a reply and ends with the operator pressing Cmd+V and Enter. It also states the negative condition clearly: "It sends nothing: no browser automation and no API call." It does not name sibling alternatives, but the when-to-use picture is complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.