Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Get function url

supabase_get_function_url
Read-only

Retrieves the full invocation URL for a Supabase Edge Function by site and function name, so you can call the function endpoint directly.

Instructions

[UNIFIED] Get the full URL for invoking an Edge Function.

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>",
      "function_name": "<function_name>"
    },
    "name": "supabase_get_function_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
function_nameYes

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?

The readOnlyHint annotation already tells the agent this is a safe read with no side effects, so the description's main added value is clarifying that the output is an invocation URL. It does not say whether the URL is authenticated, time-limited, or requires the function to be deployed. With annotations covering the safety profile, this is adequate but thin.

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 that states the core purpose immediately with no filler. The only waste is the "[UNIFIED]" tag, which adds no information for an agent.

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?

There is no output schema, so the description carries the burden of describing the returned value, and it does so only as "full URL" without format, auth, or expiry details. Combined with two required but undocumented parameters, an agent cannot call this confidently beyond guessing.

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% and both parameters are required, yet the description says nothing about them. In particular "site" is ambiguous — project reference, region, or base URL — and that ambiguity is left entirely unresolved. The description therefore fails to compensate for the schema gap.

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?

"Get the full URL for invoking an Edge Function" gives a specific verb and resource, so the agent knows this returns an invocation URL rather than executing anything. It does not distinguish itself from close siblings like supabase_get_public_url or supabase_get_function_info, which is the only thing keeping it from a 5. The "[UNIFIED]" prefix is noise that carries no meaning.

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 states what the tool returns but never says when to call it versus supabase_invoke_function, supabase_get_public_url, or supabase_get_function_info. There are no prerequisites, no exclusions, and no indication of what happens if the function does not exist. Usage must be inferred entirely from the name.

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