Skip to main content
Glama

Send a LinkedIn message (REAL, 3 credits)

send_linkedin_message

Send a REAL LinkedIn message in the chat; costs 3 credits, the AI stops messaging this contact (human takeover) and the CRM lead moves to Manager Dialog. Only after the user approved preview_send_linkedin_message.

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": "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 full behavioral burden and discloses key consequences: 3 credits are consumed, the AI stops messaging the contact via human takeover, and the CRM lead moves to Manager Dialog. It does not explicitly state reversibility or permission/account requirements, but the major side effects are well covered.

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 description is compact and front-loaded: purpose first, then cost and side effects, then the required prerequisite. Every clause adds relevant information without waste.

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?

It provides strong behavioral context for a side-effectful mutation, including cost and workflow prerequisites. However, with no annotations, no output schema, and zero parameter description coverage, it leaves parameter usage and expected result/error handling undocumented.

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%, so the description must compensate. It only vaguely implies a chat and message, but does not explain chat_id, text, required formats, or constraints for either parameter.

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 uses a specific verb and resource: 'Send a REAL LinkedIn message in the chat.' It distinguishes the real send action from the preview workflow by explicitly naming preview_send_linkedin_message, so the agent can differentiate it from siblings without opening the schema.

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 a clear prerequisite: 'Only after the user approved preview_send_linkedin_message.' This explicitly routes the agent to the preview alternative before calling this tool, matching the strongest usage-guideline pattern.

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