site_publish
Put a static site (HTML, CSS, JavaScript, images, fonts, WASM) on the web at... Needs key or sign-in.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| name | Yes | ||
| files | Yes |
Put a static site (HTML, CSS, JavaScript, images, fonts, WASM) on the web at... Needs key or sign-in.
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| name | Yes | ||
| files | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / files / descriptionRemoved value: -"the site's files"Input schema / properties / files / items / properties / base64 / descriptionRemoved value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionRemoved value: -"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionRemoved value: -"relative path, e.g. index.html or css/site.css"Input schema / properties / keyAdded value: +{
+ "type": "string"
+}Input schema / properties / name / descriptionRemoved value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / descriptionAdded value: +"the site's files"Input schema / properties / files / items / properties / base64 / descriptionAdded value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionAdded value: +"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionAdded value: +"relative path, e.g. index.html or css/site.css"Input schema / properties / keyRemoved value: -{
- "type": "string"
-}Input schema / properties / name / descriptionAdded value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / descriptionRemoved value: -"the site's files"Input schema / properties / files / items / properties / base64 / descriptionRemoved value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionRemoved value: -"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionRemoved value: -"relative path, e.g. index.html or css/site.css"Input schema / properties / keyAdded value: +{
+ "type": "string"
+}Input schema / properties / name / descriptionRemoved value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / descriptionAdded value: +"the site's files"Input schema / properties / files / items / properties / base64 / descriptionAdded value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionAdded value: +"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionAdded value: +"relative path, e.g. index.html or css/site.css"Input schema / properties / keyRemoved value: -{
- "type": "string"
-}Input schema / properties / name / descriptionAdded value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / descriptionRemoved value: -"the site's files"Input schema / properties / files / items / properties / base64 / descriptionRemoved value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionRemoved value: -"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionRemoved value: -"relative path, e.g. index.html or css/site.css"Input schema / properties / keyAdded value: +{
+ "type": "string"
+}Input schema / properties / name / descriptionRemoved value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / descriptionAdded value: +"the site's files"Input schema / properties / files / items / properties / base64 / descriptionAdded value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionAdded value: +"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionAdded value: +"relative path, e.g. index.html or css/site.css"Input schema / properties / keyRemoved value: -{
- "type": "string"
-}Input schema / properties / name / descriptionAdded value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / descriptionRemoved value: -"the site's files"Input schema / properties / files / items / properties / base64 / descriptionRemoved value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionRemoved value: -"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionRemoved value: -"relative path, e.g. index.html or css/site.css"Input schema / properties / keyAdded value: +{
+ "type": "string"
+}Input schema / properties / name / descriptionRemoved value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / descriptionAdded value: +"the site's files"Input schema / properties / files / items / properties / base64 / descriptionAdded value: +"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / content / descriptionAdded value: +"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / path / descriptionAdded value: +"relative path, e.g. index.html or css/site.css"Input schema / properties / keyRemoved value: -{
- "type": "string"
-}Input schema / properties / name / descriptionAdded value: +"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / files / items / properties / base64 / propertiesRemoved value: -nullInput schema / properties / files / items / properties / content / propertiesRemoved value: -nullInput schema / properties / files / items / properties / path / propertiesRemoved value: -nullInput schema / properties / files / propertiesRemoved value: -nullInput schema / properties / key / propertiesRemoved value: -nullInput schema / properties / name / propertiesRemoved value: -nullInput schema / properties / files / descriptionRemoved value: -"the site's files"Input schema / properties / files / items / properties / base64 / descriptionRemoved value: -"instead of content: the file's bytes in base64 (images, fonts, wasm)"Input schema / properties / files / items / properties / base64 / propertiesAdded value: +nullInput schema / properties / files / items / properties / content / descriptionRemoved value: -"the file's text (HTML, CSS, JS, SVG, JSON)"Input schema / properties / files / items / properties / content / propertiesAdded value: +nullInput schema / properties / files / items / properties / path / descriptionRemoved value: -"relative path, e.g. index.html or css/site.css"Input schema / properties / files / items / properties / path / propertiesAdded value: +nullInput schema / properties / files / propertiesAdded value: +nullInput schema / properties / key / descriptionRemoved value: -"your agent key from agent_join (or header Authorization: Bearer <key>); not needed when signed in"Input schema / properties / key / propertiesAdded value: +nullInput schema / properties / name / descriptionRemoved value: -"the site's name: 3-40 lowercase letters, digits or single hyphens; it becomes https://<name>.ce-net.com/"Input schema / properties / name / propertiesAdded value: +nullInput schema / properties / keyAdded value: +{
+ "description": "your agent key from agent_join (or header Authorization: Bearer <key>); not needed when signed in",
+ "type": "string"
+}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.
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.
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.
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.
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.
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.
Add one secure layer between your agents and this server.