Skip to main content
Glama

Start account connection

start_connect

Start connecting an Instagram, Facebook, TikTok, YouTube, X, Bluesky or LinkedIn account (a personal profile or an organization Page). For Bluesky, handle (such as alice.bsky.social) starts at the account's own server; leave it out for accounts hosted on bsky.social. X returns 402 x_billing_required until the workspace has a card on file, even within the free accounts, because X is billed per API call. Past the workspace's three free connected accounts with no card on file, any platform returns 402 billing_required with details.billingUrl, where the workspace owner adds a card. For Instagram, authMethod picks Instagram Login (the default) or facebook_login, which connects through the Facebook Page linked to the account; a profile's Instagram uses one of the two. Where the deployment runs Instagram's Unified Login instead, every Instagram connect uses it and authMethod is ignored. Returns an authUrl that the account owner must open in a browser; then poll get_connect_session until the status is connected, failed or expired.

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": {
      "platform": "<platform>",
      "profileId": "<profileId>"
    },
    "name": "start_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNo
platformYes
profileIdYesA profileId from list_profiles.
authMethodNo
redirectUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "tiktok_ads",
      -  "facebook",
      -  "meta_ads",
      -  "whatsapp",
      -  "youtube",
      -  "x",
      -  "bluesky",
      -  "linkedin",
      -  "google_business_profile"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "tiktok_ads",
      +  "facebook",
      +  "meta_ads",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky",
      +  "linkedin",
      +  "linkedin_ads",
      +  "google_business_profile"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / authMethod / enum
      Previous value: -[
      -  "instagram_login",
      -  "facebook_login"
      -]New value: +[
      +  "unified_login",
      +  "instagram_login",
      +  "facebook_login"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "tiktok_ads",
      -  "facebook",
      -  "meta_ads",
      -  "whatsapp",
      -  "youtube",
      -  "x",
      -  "bluesky",
      -  "google_business_profile"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "tiktok_ads",
      +  "facebook",
      +  "meta_ads",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky",
      +  "linkedin",
      +  "google_business_profile"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "facebook",
      -  "whatsapp",
      -  "youtube",
      -  "x",
      -  "bluesky",
      -  "google_business_profile"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "tiktok_ads",
      +  "facebook",
      +  "meta_ads",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky",
      +  "google_business_profile"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / profileId / description
      Previous value: -"Defaults to the profile your API key is bound to."New value: +"A profileId from list_profiles."
    • changedInput schema / required
      Previous value: -[
      -  "platform"
      -]New value: +[
      +  "platform",
      +  "profileId"
      +]
  6. Changed2 schema fields changed
    • addedInput schema / properties / handle
      Added value: +{
      +  "maxLength": 253,
      +  "pattern": "^(?:did:(?:plc|web):[A-Za-z0-9._:%-]+|@?(?:[A-Za-z0-9](?:[A-Za-z0-9-]{0,61}[A-Za-z0-9])?\\.)+[A-Za-z](?:[A-Za-z0-9-]{0,61}[A-Za-z0-9])?)$",
      +  "type": "string"
      +}
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "facebook",
      -  "whatsapp",
      -  "youtube",
      -  "x",
      -  "google_business_profile"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "facebook",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "bluesky",
      +  "google_business_profile"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "tiktok",
      -  "facebook",
      -  "whatsapp",
      -  "youtube",
      -  "google_business_profile"
      -]New value: +[
      +  "instagram",
      +  "tiktok",
      +  "facebook",
      +  "whatsapp",
      +  "youtube",
      +  "x",
      +  "google_business_profile"
      +]
  8. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and it is a non-read-only, non-destructive operation. The description adds substantial behavior beyond that: 402 x_billing_required for X, 402 billing_required with details.billingUrl past three free accounts, the authUrl hand-off and required polling. What it does not disclose is what state changes on the workspace side, whether a partially started session expires, or what get_account shows mid-flow.

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?

Purpose is front-loaded in the first clause and the following sentences each add operational facts (platform quirks, billing gates, auth methods, polling). It is a single dense block with some sentence-level sprawl, but nearly every clause carries information an agent needs; little is redundant.

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, the description correctly discharges the burden by explaining the return value (authUrl) and the required polling loop. The main residual gaps are the unexplained redirectUrl parameter and the mismatch between the enumerated platforms and the schema enum, which matters for a 5-parameter, 12-platform tool.

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 description coverage is only 20%, so the description must carry the load. It explains handle fully (Bluesky-specific server resolution, omitting it for bsky.social) and authMethod fully (instagram_login default, facebook_login via linked Page, unified_login deployments where authMethod is ignored), which is genuinely valuable. But profileId and redirectUrl are left entirely to the schema — redirectUrl is never mentioned at all — so compensation is only partial across five parameters.

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?

Opens with a specific verb+resource ("Start connecting an ... account") and names the platforms plus the profile-vs-Page distinction, so an agent can tell this apart from get_connect_session or disconnect_account. However, the platform list in the description (Instagram, Facebook, TikTok, YouTube, X, Bluesky, LinkedIn) omits four values present in the schema enum (tiktok_ads, meta_ads, whatsapp, linkedin_ads, google_business_profile), leaving ambiguity about whether those are supported here.

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?

Explicitly states the follow-up workflow ("Returns an authUrl that the account owner must open in a browser; then poll get_connect_session until the status is connected, failed or expired") and names the sibling to use next. It also gives preconditions — a card on file for X, the three-free-account cap — but never states when NOT to use this tool (e.g., reconnecting an already-connected account vs. disconnect_account).

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