# Artifact delivery and direct links Use this guidance when a Synter skill creates, changes, or delivers an artifact. Operate through Synter MCP whenever the capability exists. The app is the user's review/edit surface, not a prerequisite for executing MCP work. Return clickable, absolute links in the final response. Do not automatically open browser tabs just to deliver an artifact; open one when requested or needed for a visual check. ## Match the artifact to its native surface | Artifact | Delivery surface | |---|---| | Campaign or media plan | Direct plan/review page plus its document editor; label each link separately. | | Written brief, strategy, report or playbook | Specific document editor; include a share/read link when one exists. | | Image, video, UGC or creative variants | The creative canvas containing the actual assets/artboards; include asset previews or downloads as supplemental links. | | Audience or lead list | Specific audience detail/builder page and its export when available. | | Landing page | Specific editor/preview and, only after verified publication, the live page. | | Active campaign | Specific campaign detail page, with the verified platform/account context. | Use URLs returned by tools or verified against the current app routes and the actual artifact identifiers. A library homepage, raw image URL, or generic Creative Studio page is not a deep link to a saved artifact. Do not invent URL parameters, substitute IDs from different resources, or expose execute tokens, API keys, or private signed-download credentials as review links. For creatives, verify that the generated assets are saved on the intended canvas or artboards. Tool generation success alone does not prove canvas persistence. If MCP cannot attach/read back the canvas, report that specific missing step and provide the valid asset preview; do not claim the creative is on the canvas. For campaign-plan tools, use the plan identifier expected by the endpoint. `publish_plan_document` currently expects the numeric plan `id` as a string; passing its UUID causes a BigInt conversion error. Its `share_url` is the plan review page and `document_url` is the associated editor. Retain links to separate supporting strategy documents and label them distinctly. Reuse existing artifacts. Do not create a duplicate plan merely to manufacture a second link, or move a draft into review solely for a URL unless that review step is within the requested work. If a requested surface does not exist, say so and create/link it only within the authorized task. Preserve and report QA/status: a saved or reviewable artifact is not necessarily approved, published, or live. Keep plan, document, canvas and asset identifiers together in the task's existing artifact metadata so follow-up edits and handoffs refer to the same objects.