Rebases a development branch on production. This will effectively run any newer migrations from production onto this branch to help handle migration drift.
Bulk support: accepts branch_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| branch_id | Yes | ||
| branch_ids | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Despite annotations being present (readOnlyHint false, destructiveHint false), the description adds behavioral context by stating that it will 'run any newer migrations from production onto this branch' and mentions bulk support. These details go beyond the schema and annotations, clarifying the side effects of applying migrations. No contradiction with annotations; the description enhances transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, consisting of two sentences. It is front-loaded with the main action and purpose, followed by a note on bulk support. No wasted words, achieving high efficiency.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 2 parameters and no output schema, the description is fairly complete. It explains the main action, the reason (migration drift), and the bulk capability. It could be more explicit about what happens to the branch after rebase or any side effects, but given the annotations and simplicity, it is adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It explains branch_ids for batched execution but does not explicitly describe branch_id, though it is inferable from the tool name and context. The mention of 'Bulk support' adds meaning to the optional array parameter, but the primary parameter is under-documented. Overall, it provides partial semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states what the tool does: 'Rebases a development branch on production.' It also explains the purpose ('to help handle migration drift') and distinguishes itself from siblings like supabase_merge_branch and supabase_reset_branch by specifying the rebase action and its migration-focused role.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context on when to use the tool: 'This will effectively run any newer migrations from production onto this branch to help handle migration drift.' It implies the use case (migration drift) but does not explicitly mention alternatives or when not to use it. Given the sibling tools, this is a clear context but lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The Supabase-prefixed tools are all distinct CRUD/lifecycle operations on different resource types (projects, branches, migrations, edge functions, etc.). The platform-level tools (authenticate, connect, marketplace, etc.) have clear non-overlapping purposes, though their names could momentarily be confused with Supabase-specific actions if an agent doesn't read descriptions.
The 29 supabase_* tools follow a consistent 'supabase_<verb>_<noun>' pattern. However, the 6 non-prefixed platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break this convention and are inconsistent among themselves, creating a mixed naming style across the set.
At 35 tools, the server is overweight. While the Supabase domain is broad (project management, database, edge functions, branches), the inclusion of 6 unrelated platform tools inflates the count. 29 domain tools still exceeds the comfortable 15-tool upper bound, making the surface feel bloated for agents to navigate.
The tool set covers core workflows: project lifecycle (create, get, list, pause, restore), branching (create, delete, list, merge, rebase, reset), SQL/migrations, edge functions, cost estimation, and advisors. However, there are notable gaps such as no delete_project, no update operations for projects or branches, and no deletion for edge functions, which leave lifecycle coverage incomplete.