Skip to main content
Glama
Sign In

Oh My Share

by io.github.shisongsong
OverviewDiscussionsAdmin

upload_site

Publish a multi-file static site from an authenticated account. Pass files as an array of {path, content} strings; the root must contain index.html or index.htm. Returns a /s// URL that serves HTML/CSS/JS/assets. Limits: 200 files, 20 MB total, 5 MB per file. Requires OAuth or an API key; site links never show the anonymous badge. Use idempotencyKey to make retries safe.

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": {
      "files": "<files>"
    },
    "name": "upload_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional comma-separated tags.
filesYesSite files. Paths are relative and must not contain .. or absolute paths.
titleNoOptional site title; defaults to "site".
expiresInNoRetention: 1h, 24h, 7d, 30d, 90d, or 0 for permanent. Default 7d.7d
descriptionNoOptional description.
idempotencyKeyNoOptional 1-128 char retry key. Reusing it with the same payload returns the original site; the edit token is only returned to the original caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"Optional 1-128 char retry key. Reusing it returns the original site instead of creating a duplicate."New value: +"Optional 1-128 char retry key. Reusing it with the same payload returns the original site; the edit token is only returned to the original caller."
    • changedInput schema / properties / title / description
      Previous value: -"Optional site title; defaults to the folder name."New value: +"Optional site title; defaults to \"site\"."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: hard limits (200 files, 20 MB total, 5 MB per file), the auth requirement, the returned /s/<id>/ URL and what it serves, and the note that links never show the anonymous badge. The idempotencyKey explanation usefully explains how to get retry safety even though idempotentHint is false — clarifying rather than contradicting the annotation.

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-loads the core action, then payload shape, then return value, then limits, then auth — a sensible order with no filler. It is dense and slightly run-on, but every clause carries operational information.

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?

With no output schema, the description still covers return value (the /s/<id>/ URL), authentication, size/count limits, the required entry file, and retry semantics. An agent has enough to call this correctly without further probing.

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 already 100%, but the description adds a non-obvious constraint absent from the schema: the file set must contain index.html or index.htm at root. It also clarifies the overall file-array payload shape and that retries are keyed by idempotencyKey.

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 — 'Publish a multi-file static site' — plus the input shape and the resulting URL. It is clearly separable from siblings like upload, list_assets, and view, which deal with other asset operations.

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 triggering context: requires OAuth or API key, root must contain index.html/index.htm, and idempotencyKey should be used for retries. It does not explicitly say when to prefer a sibling tool (e.g. upload vs upload_site), so it stops short of full alternative routing.

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

All Oh My Share toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources