Skip to main content
Glama

artifacts_refresh

Publish a new version of an artifact at the SAME URL, without sending HTML. Two kinds of artifact: one built from saved analytics cards (artifacts.create/update with analytics_card_ids) is rebuilt by passing artifact_id alone — its cards' queries re-run and the charts are redrawn; one created/updated with a template (HTML with {{placeholder}} tokens) takes data, a flat map of placeholder -> value (e.g. {"leads": "3 200", "date": "15 июля 2026"}), and every placeholder must have a value. Ideal for a scheduled refresh of live numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoFlat map of {{placeholder}} name -> value. Every placeholder in the template must be present. Values are HTML-escaped.
labelNoOptional version label (e.g. 'daily refresh').
artifact_idYesThe data-driven artifact to refresh.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "artifact_id",
      -  "data"
      -]New value: +[
      +  "artifact_id"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources