Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

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, wechat, 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNoChannel id, e.g. 'email', 'telegram_bot', 'whatsapp'. Omit for the catalogue.
credentialsNoThe fields credential_fields asked for. Never echoed back.
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
    • 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"
+}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare this is a non-read-only, open-world, non-idempotent write, but the description adds critical behavior the annotations cannot: that unsupported channels still return success with needs_person=true plus a link, that credential_fields drive what to ask the user, that credentials are never echoed back, and that in_workspace stores nothing. This is far beyond annotation coverage.

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 the core action, then progressively details the three modes and the exclusions. Dense and information-rich, with the only mild cost being the long enumeration of unsupported channels, which is nonetheless load-bearing.

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?

No output schema exists, so the description carries the burden of describing returns (needs_person, the connect link, credential_fields) and does so explicitly. Combined with the mode breakdown and exclusions, an agent has everything needed to call this correctly and advise the user afterward.

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 baseline is 3, but the description adds real semantic value by explaining how the `channel` and `credentials` parameters behave across the three modes and what `credentials` must contain (the fields credential_fields asked for). It complements rather than merely restates the schema.

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 specific verb+resource (connect a messaging channel to this workspace) and immediately distinguishes itself from siblings like channels_list and channels_get_profile by framing itself as both a connector and a catalogue lookup. The catalogue/learn/connect tri-mode framing makes the tool's scope unambiguous.

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?

Explicitly enumerates the three calling modes (no channel, channel only, channel+credentials) and spells out which channels cannot be connected here, redirecting QR/phone/browser-signin channels to the hosted dialog and website widgets to widgets.create. This is textbook when/when-not/alternative guidance.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources