Tool reference · Workspace

connect_linkedin_account

Connect a LinkedIn account to this workspace. Returns a sign-in link, valid for 24 hours, for the PERSON to open and sign in to LinkedIn on the provider's hosted page; the account is added when they finish. Give the person the URL. Never ask them for their LinkedIn password, a verification code or a session cookie — they enter those only on that page

writesreads the workspacenot rate limited

Updated 2026-09-18 · Server 2.0.0

What it does

Connect LinkedIn without leaving the conversation. The agent asks for a link and gives it to the person; the person signs in on the provider's page, where LinkedIn's own checks — a verification code, an approval in the LinkedIn app — happen too. The agent never sees a password, and the account is added only because a person signed in.

Arguments

None. Send an empty arguments object.

This table is generated from the literal inputSchema that tools/list returns, so what your client sees and what this page says are the same object:

inputSchema
{
  "type": "object",
  "properties": {}
}

Request

Paste this, swap the key, and you have called the tool.

curl
curl -s https://topclozer.com/api/mcp \
  -H "Authorization: Bearer tcz_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "connect_linkedin_account",
      "arguments": {}
    }
  }'

Returns

{ url, expiresAt, steps[], checkWith }. url is the sign-in link to give the person; expiresAt is ISO, 24 hours out; steps are what to tell the person, in order; checkWith names the tool that shows the account once it is connected.

The payload arrives inside an MCP content block — one text block whose body is this JSON, pretty-printed. Parse the string; there is no structured-content field.

payload
{
  "url": "https://account.unipile.com/…",
  "expiresAt": "2026-10-07T09:14:03.000Z",
  "steps": [
    "Open the link within 24 hours. After that it expires and I can make a new one.",
    "Sign in to LinkedIn on that page. It is the provider's sign-in page, so your password goes there and nowhere else.",
    "If LinkedIn asks for a code, or to approve the sign-in in its app, do that on the same page or in the app.",
    "Come back and ask me to check. I will look for the account with list_sender_accounts."
  ],
  "checkWith": "list_sender_accounts"
}

Worth knowing

Makes no LinkedIn call, so it spends neither the LinkedIn budget nor a Smart Limit. The account is added when the person finishes signing in: the provider calls this server back, and the account then appears in list_sender_accounts with connected: true. A link nobody opens simply expires; call again for a new one. Which account to connect matters more than how — https://topclozer.com/mcp/accounts-for-agents compares the options. Needs the workspace:write scope.

Limits

No request limit. This tool reads the workspace database and costs nothing to serve. The limits that bite in this product are the sending controls — per-sender weekly invite caps, the warm-up ramp, the working-hours window and a randomised gap between actions — and no tool can raise them.

Related tools

All 65 tools are listed on the tool index. Connecting a client is on the Claude setup page, and the protocol details are on the server page.