ArtifactSmith

unshare

Revoke public share links for an artifact immediately; the old URL returns 404. Omit version or pass 0 to revoke every link, or specify a version to revoke only pinned links.

Instructions

Revoke public share links. Takes effect immediately; the old URL returns 404.

Permission: share.
Arguments: artifact_id (required), version (optional). A version revokes only pinned links for that version. Omit it, or pass 0, to revoke every public link, including the one that follows the latest version.
Returns: artifact_id, revoked_links (count), and state. state is "shared" when a public link is still live (with url and follows), and "not_shared" only when none is.
Example: unshare(artifact_id="art_example")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version`	No	Revoke only this version. Optional. Omit it, or pass 0, to revoke every version of the artifact.
`artifact_id`	Yes	Artifact whose public links should be revoked. Required.

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.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden and largely meets it: it discloses immediate effect, that the old URL returns 404, the required 'share' permission, and the semantics of the returned state values. Gaps remain around idempotency (calling on an already-unshared artifact) and any rate or scope limits.

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 action and its immediate effect, then structured into Permission, Arguments, Returns, and Example blocks. There is minor overlap between the argument prose and the schema descriptions, and the Returns block restates what the output schema already conveys, but nothing is padded.

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 mutation tool with no annotations, the description covers effect timing, required permission, argument semantics with edge cases, and result-state interpretation. An agent has everything needed to invoke it correctly without opening the schema.

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 100%, so baseline is 3, but the description adds meaning beyond the schema by explaining that omitting version also revokes the link that follows the latest version and that a versioned revoke targets only pinned links. That nuance about link types is not present in the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Revoke public share links'), which cleanly inverts the sibling 'share'. It does not explicitly disambiguate against adjacent siblings such as 'revoke_previews' or 'delete', so an agent must infer the boundary from the 'public share link' wording alone.

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 conditional guidance for the version argument: a specific version revokes only pinned links for that version, while omitting it or passing 0 revokes everything including the latest-version link. It stops short of naming an alternative tool or stating when not to use this one.

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

Deploy Server