A2UI Atomic Catalog

publish_url

STORES the payload server-side and returns a SHORT shareable link. Opt-in only: requires acknowledge_storage=true — confirm with the user first that they accept operator-hosted storage (ONE WEEK retention on the public tier, revocable earlier via the returned delete_token; anyone with the link can view). target "play" (default) renders in the a2uicatalog playground by reference (no URL size ceiling); target "gas" makes the short link redirect to the public Apps Script renderer. For storage in the USER's own account use emit_deployment; for nothing-stored links use preview_url.

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": {
      "payload": "<payload>",
      "acknowledge_storage": "<acknowledge_storage>"
    },
    "name": "publish_url"
  }
}

Input Schema

Name	Required	Description
`alias`	No	optional vanity name for the link (/s/<alias>) — first-come, frees when the link expires
`target`	No	Where the short link opens: "play" (default) the a2uicatalog playground by reference, "gas" the public Apps Script renderer.
`payload`	Yes	The A2UI payload to store and share: {title, theme, blocks:[...]}, up to 100 KB serialised.
`ttl_days`	No	OPERATOR-ONLY (authenticated requests): retention override; 0 = permanent. Public tier is fixed at one week.
`acknowledge_storage`	Yes	MUST be true — affirms the user consented to server-side storage

Output Schema

Name	Required	Description
`ok`	No	True when the payload was stored.
`note`	No	Retention and viewing notes.
`error`	No	Why nothing was stored (present when ok is false, e.g. daily limit).
`target`	No	"play" or "gas".
`short_url`	No	Short shareable link.
`delete_token`	No	Pass to unpublish_url to revoke.
`stored_until`	No	Expiry date (YYYY-MM-DD) or "permanent".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the storage location, one-week public-tier retention, early revocation via the returned delete_token, public visibility of the link, and the absence of a URL size ceiling for the "play" target. The only minor gap is that idempotentHint=false and openWorldHint=true are not elaborated (e.g. whether re-publishing the same payload creates a new link).

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?

The critical facts — storage, consent gate, retention — are front-loaded in the first two clauses, and the alternative-routing sentence is placed last. It is a single dense paragraph with a few stacked parentheticals, but no sentence is wasted.

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 five-parameter mutating tool with nested payload objects, the description covers consent, retention, revocation, visibility, size behavior, and sibling routing. An output schema exists, so the delete_token's return shape need not be explained here.

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 coverage is 100%, so target, acknowledge_storage, payload, alias and ttl_days are all already documented, and the description largely restates the target and consent semantics. It does add retention framing that contextualizes ttl_days, but it says nothing about alias or the 100 KB payload limit that the schema carries.

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?

States a specific verb and effect — "STORES the payload server-side and returns a SHORT shareable link" — plus the two rendering modes ("play" by reference vs "gas" redirect). It is immediately distinguishable from emit_deployment (user-account storage) and preview_url (nothing stored).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly declares opt-in behavior and the gating requirement: acknowledge_storage=true and confirming consent with the user first. It also names both alternatives with the condition that selects each — emit_deployment for the user's own account, preview_url for nothing-stored links.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All A2UI Atomic Catalog tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.