ArtifactSmith

delete

Purge an artifact from ArtifactSmith with a two-step confirmation: first call returns a token, second call permanently removes it.

Instructions

Two-step purge of an artifact. Warn the user before the second call.

Permission: delete.
Arguments: artifact_id (required), confirm_token (optional until the second call).
Returns: first call is step "confirm" with confirm_token, title, versions, expires_in "10m", and a warning.
Second call returns deleted true, artifact_id, and purged_object_versions.
Example: delete(artifact_id="art_example") then delete(artifact_id="art_example", confirm_token="...")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`artifact_id`	Yes	Artifact to purge. Required.
`confirm_token`	No	Confirmation from the first delete call. Optional on the first call (returns a token valid for 10 minutes). Required on the second call to purge. Example: "AbCdEf...".

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the irreversible purge, the required delete permission, the 10-minute token expiry, and the returned warning. It stops short of explicitly stating permanence/irreversibility or any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the two-step nature, then uses short labeled sections (Permission, Arguments, Returns, Example) with zero filler. Every line contributes operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, annotation-free tool this covers the essentials an agent needs: confirmation flow, permission, token lifetime, and response shapes. Explaining returns is mild redundancy given the output schema, but nothing required is missing.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents confirm_token's first-call-optional/second-call-required semantics and the 10-minute validity. The description restates that flow rather than adding meaning, so the baseline 3 applies.

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+resource ('Two-step purge of an artifact') and immediately conveys the distinguishing mechanic (two-call confirmation). An agent can tell it apart from edit, revoke_previews, or unshare 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 clear procedural guidance: 'Warn the user before the second call,' and the example shows the exact call sequence. It does not, however, contrast this tool with siblings like revoke_previews or edit for partially-destructive scenarios, so it falls short of explicit alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server