pushpage
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| Authorization | Yes | pushpage API key supplied via the Authorization header, e.g. `Bearer pp_your_key_here`. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Publish HTML as shareable pages, list your pages, and delete them by ID. The id returned by publish_page can be passed directly to delete_page.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_pageA | Publish an HTML page and return its shareable URL. Returns {url, id, expires_at}. title is optional — when omitted it is extracted from the HTML tag, or falls back to 'Untitled'. expires_at is an ISO-8601 timestamp indicating when the page will be automatically deleted. |
| list_pagesA | List all pages published by the current user. Returns a list of page objects, each with id, title, url, and created_at. |
| delete_pageB | Delete a page by its id. Use the id from publish_page or list_pages. |
| healthA | Check whether the pushpage service is reachable and healthy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct action: publish (write), list (read), delete (remove), and health (service check). There is no overlap in purpose, so an agent can select unambiguously from names and descriptions alone.
publish_page, list_pages, and delete_page all follow a clean verb_noun pattern on the same resource. health is a bare noun with no verb, a small but noticeable deviation from the otherwise consistent convention.
Four tools is well-scoped for a simple page-publishing service; every tool (including the health check) earns its place with no filler or redundancy.
The surface covers create, list, and delete, but there is no update/republish operation (e.g. changing title or extending expires_at) and no get_page to fetch metadata by id. Agents wanting to modify a published page hit a dead end.