Skip to main content
Glama

Mellow Hub

by world.mellow.www
OverviewDiscussionsAdmin

Start connecting a channel

connect_channel

Returns a link a PERSON must open to connect a network. You cannot complete this yourself: every network asks a human to sign in. Bluesky is connected on Mellow Hub's Channels page, where the person types the handle and an app password; never ask for a password in the chat. Telegram is connected inside Telegram: the link opens Mellow's bot, where the person presses Start and picks their channel. Give the link and the instruction to the person, then call list_channels with refresh once they say they are done. Each profile supports one Instagram. For another Instagram, the owner must create a new profile in Hub and authorize a separate credential there.

Input Schema

NameRequiredDescriptionDefault
platformYes
connectionTypeNoInstagram: instagram or facebook. X: oauth2 or oauth1. LinkedIn: organization or personal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "instagram",
-  "tiktok",
-  "tiktok_business",
-  "youtube",
-  "x",
-  "linkedin",
-  "threads",
-  "bluesky",
-  "pinterest",
-  "facebook"
-]New value: +[
+  "instagram",
+  "tiktok",
+  "tiktok_business",
+  "youtube",
+  "x",
+  "linkedin",
+  "threads",
+  "bluesky",
+  "pinterest",
+  "facebook",
+  "telegram"
+]
  2. Changed2 schema fields changed
    • removedInput schema / properties / appPassword
      Removed value: -{
-  "description": "Bluesky only: an app password, never the account password.",
-  "type": "string"
-}
    • removedInput schema / properties / handle
      Removed value: -{
-  "description": "Bluesky only: the account handle.",
-  "type": "string"
-}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare openWorldHint/readOnlyHint=false; the description goes well beyond that by explaining the human-in-the-loop handoff, the per-network connection mechanics for Bluesky and Telegram, the prohibition on collecting passwords in chat, and the one-Instagram-per-profile constraint with its workaround.

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 critical fact (a link for a person, agent cannot complete it) is front-loaded in sentence one, and each subsequent sentence carries actionable behavior rather than filler. It is a single dense block of six sentences, so scanning is slightly harder than it needs to be, but nothing is wasted.

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 correctly explains what is returned (a link plus instructions), what the agent must do next, and the platform-specific exceptions and limitations. Nothing an agent needs to invoke this tool correctly and hand off to the human is 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 only 50%, so the description must compensate: it adds real semantic weight to the platform parameter by describing distinct flows for bluesky, telegram and instagram and the one-instagram-per-profile rule. It does not, however, explain connectionType values (instagram/facebook, oauth2/oauth1, organization/personal) at all, which is left entirely to 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?

The first sentence states a specific verb, resource and output: it returns a link that a human must open to connect a network. It also makes the crucial distinction that the agent cannot complete the task itself, which separates it from sibling tools like list_channels that merely report state.

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?

It gives clear operating context (the person must sign in, never ask for a password in chat) and an explicit follow-up step: call list_channels with refresh once the user is done. It does not name a competing tool or a when-not-to-use condition, so it is strong context rather than full alternative routing.

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

All Mellow Hub 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