Skip to main content
Glama

Account: Connect

account_connect

Get a secure connection (or reconnection) link for one of the user's provider accounts: LinkedIn, WhatsApp, Instagram, Facebook/Messenger (including selected Pages), Telegram, Google/Gmail, Microsoft/Outlook or generic IMAP email. Use when the user asks to connect/add/reconnect an account, or after a connect_account/reconnect_account result. Pass account_id only to re-authenticate an existing account (from list_connected_accounts), including a healthy Facebook account needing additional Pages or a healthy LinkedIn account needing Company Pages or a different premium product. Facebook Hosted Auth offers Messenger and administered Pages for explicit selection. LinkedIn Hosted Auth offers Classic, Company Pages, Sales Navigator and Recruiter when available; the user must select them. Sales Navigator and Recruiter cannot be active together on one connection. Afterward use linkedin_list_managed_company_pages and linkedin_list_inboxes to inspect accessible pages/products. WhatsApp and Telegram also support QR connection through whatsapp_connect / telegram_connect; account_connect returns the browser link. Never ask the user for provider passwords; the link opens the provider's own authentication.

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": {
      "provider": "<provider>"
    },
    "name": "account_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesProvider to connect. Use 'email' to let the user pick Gmail, Outlook or IMAP; 'imap' for a generic mailbox.
account_idNoNilyo connection ID (unipile_account_id from list_connected_accounts) of an EXISTING account to re-authenticate. Omit to connect a new account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "linkedin",
      -  "whatsapp",
      -  "instagram",
      -  "telegram",
      -  "google",
      -  "outlook",
      -  "imap",
      -  "email"
      -]New value: +[
      +  "linkedin",
      +  "whatsapp",
      +  "instagram",
      +  "facebook",
      +  "telegram",
      +  "google",
      +  "outlook",
      +  "imap",
      +  "email"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only indicate a non-read-only, non-destructive, closed-world mutation; the description adds substantial context beyond that: Hosted Auth selection flows for Facebook Pages and LinkedIn products, the Sales Navigator/Recruiter mutual-exclusivity constraint, follow-up tools for inspecting pages, and the security rule that provider passwords are never collected. It does not state link expiry, one-time use, or failure behavior, keeping it short of a 5.

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?

Front-loaded with purpose and trigger before the provider/product enumeration, and every sentence carries information; the dense provider lists and multi-clause sentences make it heavier than necessary, but little is redundant.

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?

With no output schema, the description compensates by stating the return value ('returns the browser link') and where to go afterward (linkedin_list_managed_company_pages, linkedin_list_inboxes). For a two-parameter auth-link tool this covers everything an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are self-documented, so the baseline is met; the description nonetheless adds meaning the schema lacks, explaining that account_id is used specifically to re-authenticate a healthy account for extra Pages or a different LinkedIn premium product, not just to repair a broken connection.

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 resource ('Get a secure connection (or reconnection) link') plus the full provider scope, and explicitly distinguishes itself from the sibling connection tools whatsapp_connect / telegram_connect by noting those use QR while this returns a browser link.

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?

Gives explicit triggers ('when the user asks to connect/add/reconnect an account, or after a connect_account/reconnect_account result'), names alternatives and when to prefer them, and states the precise condition for passing account_id versus omitting it. It even covers the non-obvious case of re-authenticating a healthy account to gain Pages or a premium product.

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.