Skip to main content
Glama

site_publish

Put a static site (HTML, CSS, JavaScript, images, fonts, WASM) on the web at... Needs key or sign-in.

Input Schema

NameRequiredDescriptionDefault
keyNo
nameYes
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / files / description
      Removed value: -"the site's files"
    • removedInput schema / properties / files / items / properties / base64 / description
      Removed value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • removedInput schema / properties / files / items / properties / content / description
      Removed value: -"the file's text (HTML, CSS, JS, SVG, JSON)"
    • removedInput schema / properties / files / items / properties / path / description
      Removed value: -"relative path, e.g. index.html or css/site.css"
    • addedInput schema / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / name / description
      Removed value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  2. Changed6 schema fields changed
    • addedInput schema / properties / files / description
      Added value: +"the site's files"
    • addedInput schema / properties / files / items / properties / base64 / description
      Added value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • addedInput schema / properties / files / items / properties / content / description
      Added value: +"the file's text (HTML, CSS, JS, SVG, JSON)"
    • addedInput schema / properties / files / items / properties / path / description
      Added value: +"relative path, e.g. index.html or css/site.css"
    • removedInput schema / properties / key
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / name / description
      Added value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  3. Changed6 schema fields changed
    • removedInput schema / properties / files / description
      Removed value: -"the site's files"
    • removedInput schema / properties / files / items / properties / base64 / description
      Removed value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • removedInput schema / properties / files / items / properties / content / description
      Removed value: -"the file's text (HTML, CSS, JS, SVG, JSON)"
    • removedInput schema / properties / files / items / properties / path / description
      Removed value: -"relative path, e.g. index.html or css/site.css"
    • addedInput schema / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / name / description
      Removed value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  4. Changed6 schema fields changed
    • addedInput schema / properties / files / description
      Added value: +"the site's files"
    • addedInput schema / properties / files / items / properties / base64 / description
      Added value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • addedInput schema / properties / files / items / properties / content / description
      Added value: +"the file's text (HTML, CSS, JS, SVG, JSON)"
    • addedInput schema / properties / files / items / properties / path / description
      Added value: +"relative path, e.g. index.html or css/site.css"
    • removedInput schema / properties / key
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / name / description
      Added value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  5. Changed6 schema fields changed
    • removedInput schema / properties / files / description
      Removed value: -"the site's files"
    • removedInput schema / properties / files / items / properties / base64 / description
      Removed value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • removedInput schema / properties / files / items / properties / content / description
      Removed value: -"the file's text (HTML, CSS, JS, SVG, JSON)"
    • removedInput schema / properties / files / items / properties / path / description
      Removed value: -"relative path, e.g. index.html or css/site.css"
    • addedInput schema / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / name / description
      Removed value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  6. Changed6 schema fields changed
    • addedInput schema / properties / files / description
      Added value: +"the site's files"
    • addedInput schema / properties / files / items / properties / base64 / description
      Added value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • addedInput schema / properties / files / items / properties / content / description
      Added value: +"the file's text (HTML, CSS, JS, SVG, JSON)"
    • addedInput schema / properties / files / items / properties / path / description
      Added value: +"relative path, e.g. index.html or css/site.css"
    • removedInput schema / properties / key
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / name / description
      Added value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  7. Changed6 schema fields changed
    • removedInput schema / properties / files / description
      Removed value: -"the site's files"
    • removedInput schema / properties / files / items / properties / base64 / description
      Removed value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • removedInput schema / properties / files / items / properties / content / description
      Removed value: -"the file's text (HTML, CSS, JS, SVG, JSON)"
    • removedInput schema / properties / files / items / properties / path / description
      Removed value: -"relative path, e.g. index.html or css/site.css"
    • addedInput schema / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / name / description
      Removed value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  8. Changed6 schema fields changed
    • addedInput schema / properties / files / description
      Added value: +"the site's files"
    • addedInput schema / properties / files / items / properties / base64 / description
      Added value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • addedInput schema / properties / files / items / properties / content / description
      Added value: +"the file's text (HTML, CSS, JS, SVG, JSON)"
    • addedInput schema / properties / files / items / properties / path / description
      Added value: +"relative path, e.g. index.html or css/site.css"
    • removedInput schema / properties / key
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / name / description
      Added value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
  9. Changed6 schema fields changed
    • removedInput schema / properties / files / items / properties / base64 / properties
      Removed value: -null
    • removedInput schema / properties / files / items / properties / content / properties
      Removed value: -null
    • removedInput schema / properties / files / items / properties / path / properties
      Removed value: -null
    • removedInput schema / properties / files / properties
      Removed value: -null
    • removedInput schema / properties / key / properties
      Removed value: -null
    • removedInput schema / properties / name / properties
      Removed value: -null
  10. Changed12 schema fields changed
    • removedInput schema / properties / files / description
      Removed value: -"the site's files"
    • removedInput schema / properties / files / items / properties / base64 / description
      Removed value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"
    • addedInput schema / properties / files / items / properties / base64 / properties
      Added value: +null
    • removedInput schema / properties / files / items / properties / content / description
      Removed value: -"the file's text (HTML, CSS, JS, SVG, JSON)"
    • addedInput schema / properties / files / items / properties / content / properties
      Added value: +null
    • removedInput schema / properties / files / items / properties / path / description
      Removed value: -"relative path, e.g. index.html or css/site.css"
    • addedInput schema / properties / files / items / properties / path / properties
      Added value: +null
    • addedInput schema / properties / files / properties
      Added value: +null
    • removedInput schema / properties / key / description
      Removed value: -"your agent key from agent_join (or header Authorization: Bearer <key>); not needed when signed in"
    • addedInput schema / properties / key / properties
      Added value: +null
    • removedInput schema / properties / name / description
      Removed value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"
    • addedInput schema / properties / name / properties
      Added value: +null
  11. Changed1 schema field changed
    • addedInput schema / properties / key
      Added value: +{
      +  "description": "your agent key from agent_join (or header Authorization: Bearer <key>); not needed when signed in",
      +  "type": "string"
      +}
  12. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the write/external-effect profile is covered. The description adds the auth requirement ('key or sign-in'), which is real value. It omits key behaviors for a publish tool: what happens when republishing the same name (replace vs new deployment), size/count limits, and whether the returned site stays live indefinitely.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded, with the resource and its accepted content types up front. But the sentence is cut off mid-thought ('on the web at...'), which is a structural defect rather than economy, and the auth note is appended without connection to the parameters.

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?

This is a mutation tool with 0% parameter documentation, a nested files schema, and no output schema to reveal the resulting URL or status. An agent still cannot tell how to encode files, whether republishing replaces a site, or what it gets back — significant gaps the description should close.

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% with three parameters, including a nested 'files' array whose per-item 'base64' vs 'content' fields are undocumented. The description's asset list hints that files are web assets but says nothing about the required 'name', how 'path' is interpreted, or when to use base64 versus plain content. It does not compensate for the coverage 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?

States a concrete verb+resource: 'put a static site ... on the web', with an explicit list of asset types (HTML, CSS, JS, images, fonts, WASM). That distinguishes it from site_unpublish and site_list well enough to select it. The trailing 'at...' truncation leaves the destination (URL/domain outcome) unresolved.

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

Usage Guidelines3/5

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

The prerequisite 'Needs key or sign-in' is genuine usage context that an agent would otherwise learn only by failing. However, there is no when-to-use/when-not guidance and no routing to alternatives such as site_unpublish (to take a site down), site_list, or the sibling publish tools app_publish/cell_publish.

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