Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Channel Connect

channel_connect

Start or reconnect a social channel by generating a sign-in link; sign in to FirstReply and the platform to create or reauthorize the channel.

Instructions

Start connecting an account that is connected by signing in on the platform: MESSENGER, INSTAGRAM, LINKEDIN, WHATSAPP, THREADS, X, TIKTOK, YOUTUBE, GOOGLE_BUSINESS, MASTODON (MESSENGER is a Facebook Page). Returns a link (authUrl): the user opens it in a browser where they are signed in to FirstReply as the organization's owner, signs in on the platform, and FirstReply creates the channel; when the login can connect several accounts (Pages, locations, ...) FirstReply asks which one. The link is valid for 10 minutes. With channelId it reconnects that channel instead: after an expired or revoked login, or to grant more capabilities. Facebook Pages grant one capability per login, so ask for one at a time (first connect, then once more with channelId for PUBLISHING). Afterwards check channel_get: publishingAuthorized tells whether posts are allowed, channel_update turns publishingEnabled on.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "channel_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the new channel as the team sees it. Required without channelId.
serverNoMASTODON: the server the account is on, e.g. mastodon.social.
platformNoThe platform of a new channel. Not needed with channelId.
channelIdNoAn existing channel to reconnect instead of creating one.
capabilitiesNoWhat the login asks for on Facebook, Instagram and TikTok (TikTok: COMMENTS on a reconnect adds the comments login). Default MESSAGING. Other platforms have one login for everything.
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that a browser link is returned, that the opener must be signed in to FirstReply as the organization owner, that FirstReply performs the channel creation and may prompt for account selection, and that the link expires after 10 minutes. The Facebook Pages one-capability-per-login quirk is exactly the kind of non-obvious behavior an agent could not infer from structured fields.

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-loads the action and platforms, then layers the flow, link lifetime, reconnect mode, and platform quirk in a sensible order. It is dense and slightly run-on, with the Facebook Pages caveat appearing late, but nearly every clause carries information an agent needs.

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?

For a non-idempotent, open-world auth-flow tool with no output schema, the description supplies the return value (authUrl), its lifetime, the user-side preconditions, and the post-call verification path. Nothing essential for correct invocation appears to be missing.

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%, so the baseline is 3, but the description adds real operational meaning: channelId switches the call to reconnect mode, and capabilities must be requested one at a time for Pages, with PUBLISHING granted on a second pass. That is behavior the enum alone does not convey.

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?

States a concrete verb and resource ('Start connecting an account', returns an authUrl) and enumerates the supported platforms, so the agent knows exactly what the call initiates. It also contrasts the two modes (new channel vs. reconnect via channelId), which separates it from channel_create, though that sibling is never named explicitly.

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?

Gives clear trigger conditions ('after an expired or revoked login, or to grant more capabilities') and prescribes the follow-up sequence (check channel_get, then channel_update to turn publishingEnabled on). It lacks explicit when-not guidance such as when to prefer channel_create or channel_refresh instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools