Skip to main content
Glama
Sign In

Shager

by ai.shager
OverviewDiscussionsAdmin

Move an account to another workspace

move_channel
Destructive

Moves a connected account, with its connection, to another workspace (client or brand) of this organization: nobody signs in again. It leaves the old workspace's groups. Posts already made for it stay in the old workspace (published ones keep their numbers there); posts there that haven't gone out won't go to it any more. The answer gives its channel_id in the new workspace (a new id when the old workspace keeps its history). It changes which client an account belongs to: confirm with your human first. (Not available in an unclaimed sandbox.)

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": {
      "workspace_id": "<workspace_id>",
      "channel_id": "<channel_id>",
      "target_workspace_id": "<target_workspace_id>"
    },
    "name": "move_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYes
workspace_idYesWorkspace id from list_workspaces
target_workspace_idYesThe workspace it moves to (list_workspaces)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructive hint, the description provides deep behavioral context, detailing the persistence of posts (stay in old workspace if published), the disconnection behavior ('nobody signs in again'), and the generation of new IDs for the new workspace. This prevents agents from making assumptions about data integrity or state changes.

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 description is detailed, which is necessary for a high-stakes mutation, but well-organized, moving from the core action to secondary effects and necessary warnings.

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?

The definition is highly complete for such a complex migration task. It addresses data persistence, access changes, and environmental prerequisites, leaving no major operational question unanswered.

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?

With 67% coverage, the schema provides a baseline of 3. The description adds significant semantic meaning by clarifying the roles of the IDs (source, target, channel being moved) and the business implication of moving the account (changing which client it belongs to).

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 tool explicitly states its function: moving a connected account and its connection between different workspaces. It is clear, highly specific, and easily distinguishable from other available tools.

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 provides critical usage guidance regarding safety and scope. It mandates human confirmation ('confirm with your human first') and specifies environment limitations ('Not available in an unclaimed sandbox').

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

All Shager 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