Skip to main content
Glama

Pagetool

Export a site to a self-contained HTML file

export_site_html
Read-onlyIdempotent

Renders a site to a single self-contained HTML file. Paying customers only: requires a signed-in bearer token and an entitlement, so anonymous drafts do not export.

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": {
      "site_key": "<site_key>"
    },
    "name": "export_site_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_keyYesThe site to export.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description adds genuinely useful gating context: bearer token and entitlement requirements. However, it says nothing about where the generated file goes, whether the call is billed, or size/render limits, so the added behavioral picture remains partial.

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

Conciseness5/5

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

Two sentences, no filler, with the core action front-loaded and the access constraint immediately following. Every clause carries decision-relevant information.

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

Completeness3/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 should clarify what the caller receives (file bytes, download URL, path) and whether large sites are truncated or time-limited. It characterizes the artifact but not the response, leaving a meaningful gap for a one-parameter export tool.

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

Parameters3/5

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

Exactly one parameter with 100% schema description coverage, so the schema already carries the semantics of site_key. The description adds no format guidance (e.g., site key vs. slug vs. ID) beyond what the schema states.

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 specific verb and resource plus the output form: renders a site to a single self-contained HTML file. That distinguishes it from inverse-direction siblings like create_site_from_html or replace_page_html, but the definition never explicitly names a sibling or boundary.

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 a clear precondition ('Paying customers only') and an explicit exclusion ('anonymous drafts do not export'), which tells the agent when the call will fail. It stops short of naming alternatives such as preview or publish tools for users who lack entitlement.

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