Skip to main content
Glama

Client: unlink one platform account

unlink_account
DestructiveIdempotent

Unlink one platform account from a client (the dashboard's client editor, clearing a field): the account stays connected to the agency and can be linked again with link_account; only this client stops using it. Call without confirm to preview.

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": {
      "client": "<client>",
      "account": "<account>"
    },
    "name": "unlink_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesClient name from list_clients
accountYes
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
account_idNoFor google_ads or meta on a client with several accounts: which one (customer id or act_…). Without it the main account is unlinked and the next one becomes main.
analytics_propertyNoFor analytics on a client with several properties: which one (its id). Without it the main property is unlinked and the next one becomes main.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "For google_ads or meta on a client with several accounts: which one (customer id or act_…). Without it the main account is unlinked and the next one becomes main.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / analytics_property
      Added value: +{
      +  "description": "For analytics on a client with several properties: which one (its id). Without it the main property is unlinked and the next one becomes main.",
      +  "type": "string"
      +}
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the key added value is the clarification that destruction is scoped to this client link only — the agency-level connection persists and can be restored. It also explains the confirm preview behavior, though it says nothing about what the preview output looks like.

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?

Two sentences, front-loaded with the core action and its scope, with the preview instruction at the end. The parenthetical UI reference ('the dashboard's client editor, clearing a field') is mildly expendable but aids recognition.

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 destructive, no-output-schema mutation, the definition covers reversibility, blast radius and the preview step, which is what an agent needs before committing. Minor gap: no mention of the main-account fallback, which only appears in the schema.

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 coverage is 80% and already documents confirm, account_id and analytics_property in detail. The description only restates the confirm-preview semantics, which the schema already spells out, so it adds little beyond the structured fields.

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 and resource ('Unlink one platform account from a client') and immediately scopes it: the account stays connected to the agency, only this client stops using it. This clearly separates it from link_account and from connect_* siblings.

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?

Explicitly routes the agent to link_account for re-linking and prescribes the preview-first call pattern ('Call without confirm to preview'). It does not name an explicit when-not-to-use case, keeping it short of 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.