Skip to main content
Glama

Delete a client

clipember_delete_client
Destructive

Delete a client. Its accounts stay connected and their posts stay scheduled — they just no longer belong to any client.

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

Input Schema

NameRequiredDescriptionDefault
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavioral context: which related entities are preserved (accounts stay connected, posts stay scheduled) and what changes (they no longer belong to a client). It stops short of stating irreversibility, permission requirements, or what happens when the clientId does not exist — relevant given idempotentHint=false.

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 short sentences with the operation front-loaded and the consequence immediately after. Every clause carries information; nothing is redundant or padded.

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 single-parameter destructive tool with full annotation coverage and no output schema, the description covers the critical side-effect story an agent needs before calling. Minor gaps remain on error/failure behavior for invalid or already-deleted clients and on permissions.

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?

There is one required parameter (clientId) with 0% schema description coverage, so the schema supplies only a UUID format and pattern, not meaning. The description refers to "a client" but never explains the parameter explicitly or whether the ID must reference an existing client; the single obvious parameter keeps this from being a larger gap.

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 opens with a specific verb and resource ("Delete a client"), which is immediately distinguishable from siblings like clipember_update_client or clipember_create_client. No ambiguity about what the operation acts on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the note that accounts and scheduled posts survive deletion hints at the intended context (removing the client grouping without losing work), but there is no explicit when-to-use/when-not guidance or named alternative such as clipember_set_account_client for reassigning accounts.

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