Skip to main content
Glama

Move an account to a client

clipember_set_account_client
Idempotent

Put one connected account (connectionId from clipember_list_platform_connections) into a client, moving it out of any other client — or pass clientId null to take it out of its client. The account stays connected either way.

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": {
      "connectionId": "<connectionId>",
      "clientId": "<clientId>"
    },
    "name": "clipember_set_account_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesTarget client, or null for no client
connectionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructiveHint=false and idempotentHint=true, so the safety bar is partly covered. The description adds genuinely non-obvious behavior beyond that: the account is removed from any other client (a side effect on prior state) and the account 'stays connected either way', which reassures the agent this is not a disconnect. It doesn't mention permissions or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core mutation front-loaded and the null-detach case and the 'stays connected' caveat placed after. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter mutation with full annotation coverage and no output schema, the description covers both parameters' meaning, the side effect, and the non-destructive nature. The only gap is that it says nothing about what a successful call returns or whether an error occurs if the clientId is unknown.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% — clientId is documented in the schema but connectionId has no description at all. The description compensates well for connectionId by naming its source tool (clipember_list_platform_connections) and reinforces the null semantics for clientId, but it adds no format or constraint detail beyond the schema's existing UUID pattern.

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 states a specific verb and resource ('Put one connected account ... into a client') and immediately clarifies the reassignment semantics ('moving it out of any other client'), which is exactly the behavior an agent needs to distinguish this from a plain create/link operation. It also points at the sibling that supplies the connectionId, grounding the resource in the sibling catalog.

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 usage context, including the two distinct modes: assign to a client, or pass clientId null to detach. It also tells the agent where to obtain connectionId. It stops short of explicit exclusions (e.g., when to use clipember_update_client or clipember_delete_client instead), so a 4 rather than a 5.

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.

Resources