Skip to main content
Glama

fs_public_url

DestructiveIdempotent

Get a public URL for a file written via fs_write. The URL is hosted on the project's subdomain at /storage/{path} and can be embedded directly as an image src, anchor href, etc. — no signing or auth. A file in a declared file collection takes its visibility from db/schema.ts: make_public on it answers FILE_VISIBILITY_DECLARED (docs({ topic: 'declared-files' })).

Files are PRIVATE by default. Asking for a public URL does NOT silently expose a private file: a private file returns an error unless you pass make_public: true to publish it. An already-public file just returns its URL. fs_signed_url gives a time-limited link to a private file WITHOUT making it world-readable.

Example:

{ "project_id": "my-saas", "path": "/uploads/users/alice/avatar.png", "make_public": true }
// Returns: { "public_url": "https://my-saas.somewhere.site/storage/uploads/users/alice/avatar.png", ... }

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": {
      "project_id": "<project_id>",
      "path": "<path>"
    },
    "name": "fs_public_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFull path with leading slash
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).
make_publicNoWorld-readable publication flag. A private file requires true for exposure; an already-public file ignores it. Omission preserves privacy and returns an error rather than silently exposing a private file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description supplies the reason: passing make_public:true makes the file world-readable and persistent. It adds non-obvious behavior beyond the annotations — the declared-file-collection visibility rule from db/schema.ts, the FILE_VISIBILITY_DECLARED error, and the pointer to docs({ topic: 'declared-files' }).

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?

Front-loaded with the core purpose in sentence one, then the privacy caveat, then the sibling contrast, then a concrete example. The example earns its place by showing the exact request and returned public_url, though the make_public explanation slightly duplicates the schema text.

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

Completeness5/5

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

There is no output schema, and the example supplies the return shape (public_url plus ellipsis). For a 3-parameter tool with a real privacy side effect, the description covers what an agent must know before calling: default privacy, the publishing flag, the error mode, and the alternative tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description still adds value by stating the resulting URL shape (/storage/{path} on the project subdomain) and by connecting make_public to the declared-file-collection error path, which is not in the schema. It repeats some of the make_public contract already documented in the schema, keeping it at 4 rather than 5.

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

Purpose5/5

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

States a specific verb and resource: get a public URL for a file written via fs_write, and immediately names the sibling it differs from (fs_signed_url). An agent can distinguish it from fs_signed_url without opening either schema.

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

Usage Guidelines5/5

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

Explicitly contrasts the two URL tools: fs_signed_url gives a time-limited link to a private file WITHOUT making it world-readable, while this tool exposes it. It also explains the private-by-default contract and that omitting make_public returns an error rather than silently exposing the file.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources