Skip to main content
Glama

Preview a manual LinkedIn message

preview_send_linkedin_message

Dry-run: recipient, exact text, cost (3 credits) and whether the balance suffices. Nothing is sent. Call before send_linkedin_message and show the text to the user.

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_id": "<chat_id>",
      "text": "<text>"
    },
    "name": "preview_send_linkedin_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
chat_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and covers the two most important traits: 'Nothing is sent' (no side effects) and the cost of 3 credits plus a balance check. It does not say what happens on an invalid chat_id or insufficient balance, so behavior at the failure boundary is left implicit.

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?

Three short sentences, front-loaded with the dry-run nature and the returned data, then the sequencing instruction. No filler and nothing buried.

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?

With no output schema and no annotations, the description usefully enumerates the preview payload (recipient, text, cost, sufficiency), which an agent otherwise could not know. The remaining gap is the opaque chat_id, which is undocumented in both schema and description.

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 0% with no parameter descriptions, so the description must compensate. It partially does: 'recipient' maps to chat_id and 'exact text' maps to text, implying the text is sent verbatim. However, it never explains what a chat_id is (a LinkedIn conversation identifier? a contact id?) or where to obtain one.

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 states exactly what the tool does: a dry-run of sending a LinkedIn message, returning recipient, exact text, cost (3 credits) and balance sufficiency. It also explicitly names the sibling it precedes (send_linkedin_message), so an agent can place it in the workflow without ambiguity.

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?

It gives an explicit sequencing rule: 'Call before send_linkedin_message and show the text to the user.' That is a real when-to-use instruction plus an interaction requirement. It does not state when to skip the preview or what to do if the preview reports insufficient balance.

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