Skip to main content
Glama

Create a LinkedIn reconnect link

create_linkedin_reconnect_link
Destructive

Use this when a LinkedIn seat shows as not connected because LinkedIn ended its session. Makes a hosted sign-in link, valid for 24 hours, that signs the seat in again; keep the link private. Signing in again costs nothing while the seat's 30 days are paid for. If they ran out while it was signed out, connecting again starts a new 30 days at $10.

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": {
      "accountId": "<accountId>"
    },
    "name": "create_linkedin_reconnect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe LinkedIn seat's id, as the list of sending accounts gives it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent, destructive mutation, and the description adds real context beyond that: the link is hosted, expires in 24 hours, must be kept private, and carries specific billing consequences. It does not explain why the call is marked destructive (e.g. whether existing links or sessions are invalidated) or that each call mints a fresh link, which is the practical meaning of idempotentHint=false.

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?

The trigger condition is front-loaded, followed by what the tool produces, then the privacy warning and the billing caveat. Every sentence carries information, though the pricing sentence is long enough to slow scanning slightly.

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 one-parameter tool with no output schema, the definition covers when to call it, what it returns (a 24-hour hosted sign-in link), handling guidance (keep private), and cost outcomes. The only meaningful gap is what happens to previously generated links and why the operation is classed as destructive.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that accountId is the LinkedIn seat's id as returned by the sending-accounts list. The description reinforces the 'seat' concept but adds no new syntax, format, or sourcing detail beyond the schema, which is the expected baseline here.

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 gives a specific verb and resource: it 'makes a hosted sign-in link' that 'signs the seat in again', scoped to a seat whose LinkedIn session ended. That is far more precise than the title alone. It does not, however, name or differentiate itself from the sibling create_linkedin_connect_link, so an agent must infer the reconnect-vs-first-connect split from the name.

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 opening clause states a clear triggering condition: use it when a seat shows as not connected because LinkedIn ended its session. It also adds a cost-based condition for when reconnecting is free versus when it starts a new paid 30-day term. It stops short of explicit exclusions or naming the alternative tool to use for a never-connected seat.

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