Skip to main content
Glama

Delete an app user, their codes and sessions

app_users_delete
Destructive

Deleted.

DELETE /api/v1/app-users/{id}

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId.

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": {
      "id": "<id>"
    },
    "name": "app_users_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the core risk is communicated without the description. Beyond that, the description only adds the multi-space routing requirement; it omits that the deletion is irreversible, that related codes and sessions are cascaded (that fact lives only in the title), and whether a confirmation step is expected.

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

Conciseness3/5

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

Three short lines with no filler, but the leading "Deleted." is wasted and confusing in its tense, and the most important information (what is destroyed) is not front-loaded. The structure is functional rather than efficient.

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

Completeness3/5

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

For a destructive two-parameter tool with no output schema, the annotations and the targetSpaceId workflow cover the essentials, but the description leaves cascade effects, irreversibility, and the meaning of the id parameter to inference. Adequate, but noticeably thin for a permanent deletion operation.

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 50%: targetSpaceId is already documented in the schema, and the description largely repeats that guidance. The required id parameter has no description anywhere, though the path template {id} implies it identifies the app user. The description adds marginal meaning beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Deleted." is a fragment that merely restates the tool name rather than describing an action, so the real signal comes from the endpoint path "DELETE /api/v1/app-users/{id}" and the title's note that codes and sessions are removed too. An agent can infer the resource and verb, but the description alone is vague about scope and does not distinguish this from siblings such as app_users_disable.

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?

The third line gives a concrete prerequisite workflow for multi-space accounts: call auth_verify, ask the user which space to use, then pass targetSpaceId. However, it never states when to prefer deletion over the sibling app_users_disable, nor any confirmation or preconditions for single-space accounts, so guidance is partial and implied rather than explicit.

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.