Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Update bucket

supabase_update_bucket
Destructive

Update a Supabase storage bucket's settings, including public access, file size limits, and allowed MIME types, to control how its files are exposed and uploaded.

Instructions

[UNIFIED] Update bucket settings like public access, file size limit, or allowed MIME types.

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>",
      "bucket_id": "<bucket_id>"
    },
    "name": "supabase_update_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
publicNo
bucket_idYes
file_size_limitNo
allowed_mime_typesNo

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
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, and the description adds nothing beyond that framing. For a destructive mutation it fails to warn that omitting fields may reset existing settings, that flipping `public` exposes all files, or that the call is non-idempotent.

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?

A single front-loaded sentence with no wasted clauses, though the '[UNIFIED]' prefix is noise that conveys nothing to the agent. The most important information is presented first.

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?

This is a destructive mutation tool with no output schema and five parameters at 0% schema coverage, yet the description is one sentence. It does not say whether updates are partial or full replacement, what happens to omitted fields, or what a successful response looks like.

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 description coverage is 0%, so the schema offers only bare names and types; the description compensates partially by mapping three of the five parameters to concrete meanings. However, the required `site` parameter and `bucket_id` are never explained, and the odd string typing of `public` and `file_size_limit` is left unaddressed.

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?

The description names a specific verb (update) and resource (bucket) and enumerates the settings that can change (public access, file size limit, allowed MIME types). It does not distinguish this from siblings like supabase_create_bucket or supabase_delete_bucket, but the operation itself is unambiguous.

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 guidance on when to use this tool versus creating a new bucket, emptying one, or updating policies. Nothing states prerequisites such as the bucket needing to exist or what permissions are required, so an agent must infer the context entirely.

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