Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Host a web page, publish HTML: a URL for your agent's output

page_publish
Destructive

Publish an HTML page and get a public URL for it (valid up to 7 days): send the HTML (up to 200,000 characters) and an optional title; the page is sanitised (no scripts, styles, frames, forms or event handlers; links and https images stay), screened by content moderation, stored, and served at /p/ with noindex. Use to hand a person a report, table or summary your agent produced, or to share results between agents. Removal requests: /support. Price $0.01/call via x402 USDC or a card key (/credits); failed calls free. Publishes a page on the public web that stays up until it expires and cannot be withdrawn; each call is charged, so repeats are not free.

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": "page_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays the page stays online, 1 to 7 (default 7)
htmlYesThe HTML to publish (body content or a full document), up to 200,000 characters
titleNoPage title (default: the first line of text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, it discloses sanitisation rules (no scripts, styles, frames, forms, event handlers; links and https images retained), content moderation, storage and noindex serving. It states cost ($0.01/call, failed calls free) and that the page cannot be withdrawn and repeats are not free, all consistent with destructiveHint=true, openWorldHint=true and idempotentHint=false.

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 return value, then constraints, then use cases and pricing, with no filler sentences. There is minor redundancy in stating price twice ("Price $0.01/call" and "each call is charged, so repeats are not free"), but the density is justified for a costly, irreversible public write.

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 tool with no output schema and only three simple parameters, the description covers everything an agent needs: what is produced (a URL), how long it lives, what the sanitisation and moderation pipeline does, cost, and irreversibility. Nothing material is missing for correct invocation.

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?

Schema description coverage is 100%, so the schema already documents html, days and title, including the 200,000-character cap and the 1–7 day range. The description restates the char limit and the seven-day validity but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

The description opens with a concrete verb and resource ("Publish an HTML page and get a public URL") and names the serving path (/p/<id>) and noindex behavior. It is clear what the tool does, but it never distinguishes itself from the sibling page_host, leaving the agent to infer which host/publish tool to pick.

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?

It gives explicit use cases ("hand a person a report, table or summary your agent produced, or to share results between agents") and a clear escape hatch for takedowns (/support). What it lacks is any negative guidance such as when a non-public or ephemeral alternative would be preferable, so the boundary against siblings remains unstated.

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.