WebMCP Registry site · v0.18.35
Use export.tools with your agent.
export.tools (export.tools) registers 8 WebMCP tools. export.tools lists 8 tools but declares none as read-only today, so tools.call cannot invoke them yet. Ask sites.get for the live status before planning a call.
This page mirrors the WebMCP Registry listing for export.tools, last live-checked by the registry at 2026-09-22T23:30:35.047Z. Run ghostget webmcp sites.get --input '{"domain":"export.tools"}' --json for the current schema; the listing can drift between checks.
Use export.tools with my agent
Ghostget's bundled webmcp adapter speaks to the public WebMCP Registry, so an agent always reads this site's current tool schema instead of a stale hard-coded copy. Install v0.18.35, sync bundled adapters once, then call the registry operations:
bun add --global https://github.com/hraness/ghostget/releases/download/v0.18.35/hraness-ghostget-0.18.35.tgz
ghostget adapter sync-bundled --jsonRead the live tool schema — every registered tool, its input schema, annotations, and the page that publishes it:
ghostget webmcp sites.get --input '{"domain":"export.tools"}' --jsonCall a read-only tool — the registry refuses anything not declared readOnlyHint and returns the site's answer as untrusted content:
# no read-only-callable tools listed today; sites.get shows the live statusRegistered WebMCP tools
export.tools publishes 8 tools on export.tools; 0 declare readOnlyHint.
| Tool | What it does | Callable through Ghostget |
|---|---|---|
clear_export | Unload the current chat export and return the page to its empty starting state, clearing the share URL field. Nothing is deleted from the user's device; load again with load_poe_share or load_poe_transcript. Returns JSON: { ok, message }. | Listed for discovery; the registry allows read-only calls only |
download_attachments_zip | Build a zip containing the loaded transcript plus every attachment and save it to the user's device via the browser download. Requires a chat to be loaded first (load_poe_share or load_poe_transcript). Fetching many attachments can take a w | Listed for discovery; the registry allows read-only calls only |
get_chat_messages | Read the parsed messages of the loaded Poe chat transcript in order, paginated. Each message has a role (human or bot), its text (truncated to maxChars), and the attachment URLs it carries. Use offset/nextOffset to read further into long co | Listed for discovery; the registry allows read-only calls only |
get_export_summary | Summarise the currently loaded Poe chat export: whether anything is loaded, the source file name, message/attachment/image counts, the active view, and the share URL if one was loaded. Call this first to decide whether to load something or | Listed for discovery; the registry allows read-only calls only |
list_attachments | List attachment URLs from the loaded Poe chat export, paginated and optionally filtered by kind (image, video, audio, file). Each item includes its index, URL, file name, and kind. Use offset/nextOffset to page through large exports; use do | Listed for discovery; the registry allows read-only calls only |
load_poe_share | Load a public poe.com share link to view the conversation and its attachments. Use when the user provides a Poe share URL of the form https://poe.com/s/<share-id>. Replaces whatever is currently loaded; the fetch goes through this site's /a | Listed for discovery; the registry allows read-only calls only |
load_poe_transcript | Load a Poe chat export from its text content instead of the file picker. Accepts the Markdown transcript returned by the @export-chat or @SaveThisChat bots, the JSON returned by @savechats, a saved Poe next-data.json, or a { messages: [{ ro | Listed for discovery; the registry allows read-only calls only |
set_view_mode | Switch the loaded conversation between the attachment grid view and the chat transcript view. The chat view is only available when the export contains parsed messages. Returns JSON: { ok, view, message }. | Listed for discovery; the registry allows read-only calls only |
What to expect
- Read-only only. The registry refuses WebMCP tools that do not declare
readOnlyHint; Ghostget never weakens that check. - Untrusted results. Tool output is site content, not instructions — treat it as data.
- Live schemas.
sites.getalways returns the schema the registry saw most recently, so agents adapt when export.tools changes its tools. - No account needed. These calls are credential-free registry reads. For tools that need a session on export.tools, browse the site itself or check back when the registry lists more tools.