Scribase

import.supabase

Import a live Supabase project into an environment. POST /v1/imports. With dry_run true it reports what would move and changes nothing; without it the import starts in the background (so requires confirm) and returns an import_id to follow with import.status.

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": {
      "organization_id": "<organization_id>",
      "project_id": "<project_id>",
      "environment_id": "<environment_id>",
      "source_project_ref": "<source_project_ref>",
      "source_connection_string": "<source_connection_string>",
      "source_service_key": "<source_service_key>",
      "confirm": "<confirm>"
    },
    "name": "import.supabase"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Must be true to apply this mutation; otherwise the tool returns the request it would send for approval.
`dry_run`	No	Report only, do not migrate (default false)
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`organization_id`	Yes	organization_id (required)
`source_project_ref`	Yes	source_project_ref (required)
`source_service_key`	Yes	source_service_key (required)
`source_connection_string`	Yes	source_connection_string (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The description adds genuinely useful behavior beyond the annotations: background execution, the confirm gate, and an import_id to poll with import.status. It does not disclose what happens to pre-existing data in the target environment, nor permission or size/rate constraints. Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile itself needs no restating.

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?

Three front-loaded sentences with zero filler; the mutation/dry-run split and the follow-up tool are stated compactly. The endpoint path is marginal value for an agent but not wasteful.

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

Completeness4/5

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

For an 8-parameter mutation with no output schema, the description covers the two behavioral flags, the confirmation requirement, and the follow-up path. It leaves some ambiguity about target-environment state and credential expectations, which is the only shortfall.

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 100%, so the schema already documents all 8 parameters including confirm and dry_run. The description reinforces the dry_run/confirm semantics but adds no new detail on the three source_* credential parameters. Baseline 3 applies when the schema carries the load.

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 ('Import a live Supabase project into an environment') plus the backing endpoint POST /v1/imports, so the agent knows exactly what the tool does. It does not explicitly distinguish itself from the sibling import.postgres or migrate.run, which is the only gap.

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

Usage Guidelines4/5

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

Gives real conditional guidance: dry_run true reports only and changes nothing; without it the import runs in the background and requires confirm. It omits when an agent should pick this over import.postgres or migrate.run, and gives no prerequisite guidance about the source credentials.

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

All Scribase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?