Skip to main content
Glama

Publish a private web page

create_page

Publish an HTML document to a private, unguessable miinideck link and return the shareable URL. Use this whenever the user wants to share, publish, host, send, or get a link for an HTML page, report, slide deck, or artifact you produced. Pass the COMPLETE, self-contained HTML document (including ) as html. Optionally file it under a project by name with project (call list_projects first to see existing ones). SIZE LIMIT: this tool carries the whole document as a text argument, so it only fits pages you can output in one response — roughly under ~100 KB. For a LARGER file (or a ZIP / PDF / image), do NOT call this tool (the HTML would be truncated): if you can run shell commands, use prepare_upload → curl → finish_upload, which send the file's real bytes with no text-size limit; otherwise tell the user to upload it with the miinideck CLI (npx miinideck deploy <path>) or the web uploader at miinideck.com.

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": {
      "html": "<html>"
    },
    "name": "create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesThe complete, self-contained HTML document to publish.
titleNoOptional human title shown in the owner's dashboard.
expiryNoWhen the link expires. Default 'never' (Free tier falls back to 7 days unless an always-on slot is free).
projectNoOptional project (folder) to file this page under, BY NAME. Matches one of the user's existing projects case-insensitively, or creates a new project with this name if none matches. Omit to use the default Inbox.
passwordNoOptional password a viewer must enter to open the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the size ceiling and that exceeding it truncates the HTML, that links are private and unguessable, and that the return value is the shareable URL. It does not cover auth/permission requirements or what happens on quota/expiry failure, which keeps it off a 5.

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 purpose and trigger intents, then escalation paths, with caps-labeled callouts for the HTML requirement and size limit. Dense and mostly waste-free, though the size/fallback passage is long enough to slightly dilute the core instruction.

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?

For a single-action mutation tool with no annotations and no output schema, it supplies everything an agent needs: payload format, size boundary with the exact failure mode, sibling routing for oversized content, return value, and preconditions for the project parameter.

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 real meaning by stressing the html must be complete and self-contained including the doctype, and by instructing the agent to call list_projects before using project. It leaves title, expiry, and password entirely to the schema.

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?

Opens with a specific verb+resource+effect: publishing an HTML document to a 'private, unguessable miinideck link' and returning a shareable URL. It is clearly distinguishable from siblings like get_page, list_pages, and especially prepare_upload, which it names as the alternative path.

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 enumerates trigger intents ('share, publish, host, send, or get a link') and then states when NOT to use it: files larger than ~100 KB, ZIP/PDF/image payloads, with a named alternative (prepare_upload → curl → finish_upload) and a fallback for agents without shell access.

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