Skip to main content
Glama

Update a pad

update_pad
DestructiveIdempotent

Replace the HTML of a pad you published, using the edit token returned by publish_html. Saving also resets its 90 days.

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": {
      "address": "<address>",
      "edit_token": "<edit_token>",
      "html": "<html>"
    },
    "name": "update_pad"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesThe new HTML, up to 512 KB.
addressYesThe pad address, as in htmlpad.org/<address>/.
edit_tokenYesThe edit token returned when the pad was published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover destructiveHint=true, idempotentHint=true, and non-read-only status, so the bar is lower, yet the description still adds real context: the edit token is the authorisation mechanism and 'Saving also resets its 90 days' discloses a side effect on expiry that the annotations cannot express. It stops short of saying whether the replacement is atomic or what a stale token returns.

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 short sentences, front-loaded with the action and immediately followed by the one behavioural trait an agent could not infer. Nothing is wasted or buried.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter destructive write with no output schema, the description plus rich schema covers nearly everything needed to invoke it correctly. The remaining gap is failure behaviour with an invalid or expired token, and the fact that the whole HTML is replaced rather than merged is only implied by 'Replace'.

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%, including the 512 KB limit and the definition of address and edit_token, so the schema already carries parameter meaning. The description only restates the token's provenance, which the schema itself documents, adding no new syntax or format detail.

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?

The description states a specific verb and resource ('Replace the HTML of a pad you published') and scopes it to pads already published, which implicitly separates it from publish_html (first publish) and get_pad (read). An agent can tell which of the three it wants without opening another schema.

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?

It establishes the prerequisite (the edit token returned by publish_html) so the agent knows this only applies to a pad it already owns, but it never states when not to use it or what to do if the token is lost. Usage is implied rather than spelled out.

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