Skip to main content
Glama

channels_connect

🔌 Connect a messaging channel to this workspace, or find out how.

Call with no channel for the catalogue: every channel, its connect_mode and its link. Call with channel only to learn what to ask the person for (credential_fields). Call with channel + credentials to connect a credentials channel: email over IMAP with an app password, telegram_bot with a bot token, line with the channel access token and channel secret, avito.

Channels that need a QR scan, a phone code or a browser sign-in (telegram, whatsapp, instagram, facebook, email (Google sign-in), youtube, tiktok, x, threads, linkedin, zalo, maxru, the voice carriers) cannot be connected from here: the tool answers success with needs_person=true and the link https://dialogbrain.com/connect/, which opens the connection dialog for that channel. Give the person that link; do not tell them to look for it in settings. A website widget is not connected here at all: use widgets.create.

channel='google_drive' (owner/admin) creates the workspace's Google Drive address, or returns it when it exists: the person shares a folder (or a Shared Drive) with that address as Editor, then drive.folders(action='add', link=) registers it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "channels_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoChannel id, e.g. 'email', 'telegram_bot', 'whatsapp'. Omit for the catalogue.
credentialsNoThe fields credential_fields asked for. Never echoed back. `password` takes a clip:<id> handle from clipboard.copy (source {message_id, pattern: 'password'}) in place of the value, so a password a person sent in a chat is connected without being read.
display_nameNoName for the account in the channel list.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / credentials / description
      Previous value: -"The fields credential_fields asked for. Never echoed back."New value: +"The fields credential_fields asked for. Never echoed back. `password` takes a clip:<id> handle from clipboard.copy (source {message_id, pattern: 'password'}) in place of the value, so a password a person sent in a chat is connected without being read."
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, and the description adds substantial context beyond them: the needs_person=true success response with a link, the instruction not to point people at settings, that credentials are never echoed back, and the clip: handle substitution for passwords. It stops short of describing failure modes or what a partial/failed connect returns, which keeps it from 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?

The three-mode structure is front-loaded and each paragraph maps to a distinct case, so it is easy to scan. It is dense and long, and the google_drive paragraph packs two operations into one block, but no sentence is filler.

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 complex, multi-mode, open-world tool with no output schema, the description covers the catalogue path, the credential-discovery path, the connect path, the human-handoff path, and the special google_drive path. An agent has everything needed to pick the right mode and act on the result.

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 meaning: it explains the semantics of omitting `channel` (catalogue) versus supplying it alone (credential_fields) versus pairing it with `credentials`, and gives concrete channel ids and credential shapes (IMAP app password, bot token, channel access token + secret). This goes beyond the schema's per-field text.

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?

The description opens with a specific verb+resource ('Connect a messaging channel to this workspace') and then enumerates three distinct call modes (no channel = catalogue, channel only = credential_fields, channel+credentials = connect). It explicitly distinguishes itself from siblings widgets.create and drive.folders, so an agent can route correctly without opening any schema.

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?

It gives explicit when-to-use guidance for each invocation shape and names the alternatives: 'A website widget is not connected here at all: use widgets.create' and the drive.folders(action='add') follow-up for google_drive. It also states the exclusion set (QR/phone-code/browser-sign-in channels) and what to do instead (hand over the connect link).

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.