Skip to main content
Glama

Share as a tracked link

send_artifact
Destructive

Share or send a document, deck, HTML page or Claude artifact as a tracked link: the user then sees who opened it, how far they read, time per section and what they asked. For a Claude artifact, give its complete code: html for an HTML artifact, react for a React artifact. Or Markdown, a PDF/Word/PowerPoint/Excel file as document, a video as video_url, or a public URL: a page, or a file's download link (a PDF, Office file, image or video from Gamma, Carbone, Descript and the like) which is fetched once. A ChatGPT site (an address ending in .chatgpt.site) or a shared Claude Sheet, Whiteboard or Data link opens where it lives, behind the door, with opens counted. Returns the link and its settings. Pass link to update an existing link in place (same URL, new content).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public page to copy, or the download link of a PDF, Office file, image or video (fetched once, so one-time links work).
htmlNoComplete HTML document.
linkNoOptional. Update this link instead of making a new one.
allowNoOnly these emails or domains can open it, e.g. ["@sequoiacap.com", "dana@acme.com"].
filesNoFiles the page loads by relative path (images, video, fonts), e.g. media/demo.mp4. Up to 10 MB each, 40 MB in all.
reactNoA React artifact's complete code: one file with a default export. Tailwind classes and imports from react, lucide-react, recharts, lodash, d3, mathjs, papaparse, date-fns, three, chart.js and framer-motion work. Not shadcn/ui (@/components).
titleNo
accessNopublic: anyone with the link. email: reader types an email (fake and throwaway addresses are refused). verified: reader proves the email, with Google or a 6-digit email code.
folderNoPut it in this folder on my Files page, by name. Made if it does not exist. Leave out to keep it outside folders.
notifyNoEmail me when someone opens it the first time. Default true.
documentNoA PDF, Word, PowerPoint or Excel file instead of HTML. Readers get pages, slides or sheets.
markdownNoA Markdown file's complete text (a README, plan, report or notes). It becomes a clean page: headings, tables, task lists, GitHub callouts, highlighted code and mermaid diagrams. Images it loads by relative path go in files.
downloadsNoReaders get a Download button for a PDF, Office file, image or video. Default false.
video_urlNoA video or audio file to share: the public address of an mp4, webm or mov video, or an mp3, m4a or wav audio file, up to 200 MB, such as the download link a video or voice tool (HeyGen, Higgsfield, Runway, ElevenLabs, a screen recorder) returns. The reader gets a player; the report shows how much each viewer watched or listened to and which parts. For a video file on this computer, use start_upload instead.
ai_readingNoWhat a reader's own AI (Claude, ChatGPT) may take. questions (default): only the parts that answer each question, so I see every question and no full copy leaves. full: the whole text, marked with the reader's email. off: no AI reading.
expires_in_daysNoClose the link after this many days.
discourage_screenshotsNoBlur the page when the reader switches away, block printing and copying, and watermark it with their email. No website can fully stop a screenshot. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / folder / description
      Previous value: -"Put it in this folder on my Artifacts page, by name. Made if it does not exist. Leave out to keep it outside folders."New value: +"Put it in this folder on my Files page, by name. Made if it does not exist. Leave out to keep it outside folders."
  2. Changed2 schema fields changed
    • addedInput schema / properties / markdown / description
      Added value: +"A Markdown file's complete text (a README, plan, report or notes). It becomes a clean page: headings, tables, task lists, GitHub callouts, highlighted code and mermaid diagrams. Images it loads by relative path go in files."
    • changedInput schema / properties / video_url / description
      Previous value: -"A video to share: the public address of an mp4, webm or mov file, up to 200 MB, such as the download link a video tool (HeyGen, Higgsfield, Runway, a screen recorder) returns. The reader gets a player; the report shows how much each viewer watched and which parts. For a video file on this computer, use start_upload instead."New value: +"A video or audio file to share: the public address of an mp4, webm or mov video, or an mp3, m4a or wav audio file, up to 200 MB, such as the download link a video or voice tool (HeyGen, Higgsfield, Runway, ElevenLabs, a screen recorder) returns. The reader gets a player; the report shows how much each viewer watched or listened to and which parts. For a video file on this computer, use start_upload instead."
  3. Changed2 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"A public page to copy."New value: +"A public page to copy, or the download link of a PDF, Office file, image or video (fetched once, so one-time links work)."
    • addedInput schema / properties / video_url
      Added value: +{
      +  "description": "A video to share: the public address of an mp4, webm or mov file, up to 200 MB, such as the download link a video tool (HeyGen, Higgsfield, Runway, a screen recorder) returns. The reader gets a player; the report shows how much each viewer watched and which parts. For a video file on this computer, use start_upload instead.",
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / discourage_screenshots
      Added value: +{
      +  "description": "Blur the page when the reader switches away, block printing and copying, and watermark it with their email. No website can fully stop a screenshot. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / downloads
      Added value: +{
      +  "description": "Readers get a Download button for a PDF, Office file, image or video. Default false.",
      +  "type": "boolean"
      +}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true; the description adds real behavioral context beyond that: the link is tracked with per-reader analytics, remote URLs are 'fetched once', access modes gate entry, and passing `link` overwrites content at the same URL. It never explicitly warns that this publishes content externally or that in-place updates destroy prior content, which is the main remaining gap.

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?

Front-loaded with the core action and the payoff, then organized by input type. Some sentences run long and nest examples ('a PDF, Office file, image or video from Gamma, Carbone, Descript and the like'), but nearly every clause carries usable information.

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 17-parameter tool with no output schema, the description covers the source variants, the update path, and states what is returned ('the link and its settings'). Access-control and AI-reading options rely on the schema, which is well documented, so an agent has enough to call it correctly.

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

Parameters4/5

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

Schema coverage is 94%, so the baseline is 3; the description still earns above that by constraining `react` (single file, default export, allowed libraries, no shadcn/ui) and `markdown` (GitHub callouts, mermaid, relative images via `files`) in ways the schema does not. It says little extra about `access`, `ai_reading`, or `folder` beyond the schema text.

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 resource ('share or send a document, deck, HTML page or Claude artifact as a tracked link') and immediately names the payoff (opens, read depth, time per section, questions asked). It enumerates the accepted source types so an agent can tell this apart from upload/update siblings without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete routing for input types ('For a Claude artifact, give its complete code', 'For a video file on this computer, use start_upload instead') and explains the in-place update path via `link`. It stops short of naming update_link or link_report as alternatives, so the when-to-use map is clear but not exhaustive.

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