Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Ban user

supabase_ban_user
Destructive

Ban a Supabase user for a specified duration to prevent sign-in access. Use it to block accounts temporarily or permanently during moderation or security incidents.

Instructions

[UNIFIED] Ban a user for a specified duration. Banned users cannot sign in.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
user_idYes
durationNonone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the mutation profile is covered. The description adds genuine value by stating the effect on sign-in, but omits important behavioral detail: whether existing sessions/tokens are revoked, whether the ban is reversible and how, and whether a missing duration means permanent. The ambiguity around the "none" default is left unresolved.

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 tight, front-loaded sentences with no filler; the consequence of banning is placed immediately after the action. The "[UNIFIED]" prefix is noise but negligible.

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

Completeness2/5

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

For a destructive, non-idempotent mutation with no output schema and zero schema description coverage, the definition is thin. An agent still cannot tell how to format duration, whether "none" means permanent, or whether unbanned restoration is possible, all of which matter before invoking a destructive call.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must carry the burden and does not. It mentions duration conceptually but never states the accepted format (seconds? ISO 8601? "24h"?) or what the default "none" means, and gives no hint about site or user_id semantics.

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

Purpose4/5

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

States a specific verb and resource ("Ban a user") plus the observable consequence ("cannot sign in"), which clearly separates it from sibling supabase_unban_user. It does not name the counterpart tool explicitly, so sibling differentiation is implied by the verb rather than stated.

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?

There is no when-to-use or when-not-to-use guidance: no mention of unban_user for reversal, no prerequisites, no note about whether banning requires admin scope or supersedes other user-management calls. Only the implied context of the verb itself guides selection.

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

Deploy Server

Other Tools