Skip to main content
Glama

Publish canvas

publish_canvas
Destructive

Publish a canvas artifact you presented with canvas_present at a public URL on the Ankra pages host, so the person can share it with someone who has no Ankra account. Pass the artifact_id canvas_present returned; the tool publishes the latest version you presented in this conversation (edits the person made by hand in the canvas panel are not seen here - they use the Publish button in the panel). Only html, svg and markdown artifacts can be published; javascript, json, yaml and text cannot. The page is a static snapshot served in a sandbox: its scripts run with no network, cookies or storage, window.ankra live data is not available, and a fixed notice names it as an AI-generated page published by an Ankra user. Anyone with the link can view it until it expires (ttl_hours, default 7 days, at most 30). Publishing the same artifact again keeps the same URL and extends the expiry. An organisation can have 50 live pages at once. The person approves the publication on a confirmation card before it goes public. Undo with unpublish_canvas.

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": {
      "artifact_id": "<artifact_id>"
    },
    "name": "publish_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttl_hoursNoHow long the page stays up, in hours. Omit for the default of 7 days.
artifact_idYesThe artifact_id a canvas_present call in this conversation returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

With annotations only flagging the mutation profile, the description carries real weight: it discloses that the page is a static snapshot, that scripts run with no network/cookies/storage, that window.ankra data is unavailable, that a fixed AI-generated notice is attached, that the link is world-readable until expiry, and the 50-live-page org quota. It does not explicitly say the call returns the public URL, which is the one behavioral detail left implicit.

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 publish action and input are front-loaded, and nearly every clause carries a non-obvious constraint. It is long and dense for a two-parameter tool, but very little is filler; the TTL and re-publish details could be merged more tightly.

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?

No output schema exists, so the description should say what comes back; it implies a public URL but never states the return value. Everything else an agent needs before calling — preconditions, type restrictions, sandbox semantics, quota, expiry, approval, undo — is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the prose adds meaning: artifact_id must be the one a canvas_present call returned and represents the latest presented version (not hand edits), and ttl_hours is restated as default 7 days with a 30-day cap, clarifying behavior on re-publish (same URL, expiry extended).

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 opens with a specific verb and resource ('Publish a canvas artifact ... at a public URL on the Ankra pages host') and ties it to canvas_present as the producer of the input, making it immediately distinguishable from canvas_present and unpublish_canvas.

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?

It states when to use this tool (share with someone without an Ankra account), names the alternative path for hand-edited canvases ('they use the Publish button in the panel'), gives the undo route (unpublish_canvas), and notes the person must approve on a confirmation card.

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.