{"version":"2.1.312","anchor":"artifact-publish-artifacts-mcp-helpers-and-template-telemet","canonical_anchor":"artifact-publish-artifacts-mcp-helpers-and-template-telemet","heading":"Artifact publishing returns fewer details and adds tool-action groups","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/artifact-publish-artifacts-mcp-helpers-and-template-telemet","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Artifact publishing returns fewer details and adds tool-action groups\n\nPublishing an artifact no longer returns workshop details, and Claude Code now groups the Artifacts MCP actions, including a read-only set\n\n**What**\n\nAn artifact is content that Claude creates and publishes, such as a page. Several things changed in how artifacts are published:\n\n- Tool input: a stray trailing `<\/invoke>` is now stripped from tool arguments.\n\n- Action groups: Claude Code defines groups of Artifacts MCP actions, including `publish_files`, `declare_capabilities` and `authorize_upload`, with a separate read-only group.\n\n- Publish result: it no longer includes the workshop details it used to return.\n\n- Usage reporting: reports about republishing an artifact no longer note the plain template.\n\n**Why**\n\nThe artifact tools behave a little differently, and the publish result returns fewer fields.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}