Aliyun RDS Supabase MCP Server

Official

by aliyun

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

delete_auth_user

Deletes a user from Supabase authentication using the Admin API. Requires the service role key and the user's UUID.

Instructions

Deletes a user using Supabase Admin API. Requires service role key.

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": {
      "user_id": "<user_id>"
    },
    "name": "delete_auth_user"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	The UUID of the user to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jul 14, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool deletes a user but does not disclose whether the action is irreversible, if there are cascading effects, or any side effects. The security note about service role key is helpful but insufficient for a destructive operation.

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?

The description is a single sentence with 9 words, directly stating the purpose and a key prerequisite. Every word earns its place, and it is front-loaded with the action.

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?

The tool is simple with one parameter and no output schema, so the description is mostly adequate. However, it lacks important behavioral context (e.g., irreversibility) that would fully prepare an agent for using this destructive tool.

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?

The input schema has 100% coverage, fully describing the only parameter 'user_id' as a UUID. The tool description adds no additional meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 clearly states the verb 'deletes' and the resource 'a user using Supabase Admin API', which is specific and distinguishes it from sibling tools like create_auth_user or update_auth_user.

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

Usage Guidelines2/5

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

The description mentions the requirement for a service role key, which is a prerequisite, but provides no explicit guidance on when to use this tool versus alternatives (e.g., update_auth_user for disabling users). No when-not or contextual usage notes.

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