Skip to main content
Glama

Unpin an Artifact

unpin_artifact
Idempotent

Take an Artifact off the Pinned shelf of the user's own Artifacts library. The Artifact itself is untouched.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artifact_id": "<artifact_id>"
    },
    "name": "unpin_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_idYesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….

Output Schema

NameRequiredDescriptionDefault
urlNo
titleNo
pinnedYes
artifact_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint false, idempotentHint true, destructiveHint false). The description adds real value by confirming 'The Artifact itself is untouched' and by restricting scope to the caller's own library, but it says nothing about behavior when the artifact is not pinned or not owned.

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?

Two short sentences, front-loaded with the action and scoped constraint, with the reassurance sentence placed second. No wasted wording.

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

Completeness4/5

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

For a single-parameter, idempotent, non-destructive tool with a fully documented schema and an output schema, the description covers what the agent must know before calling. The only omission is the not-pinned / not-owned edge case, which is minor at this complexity.

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 description coverage is 100% and the artifact_id property already explains the id format and link position. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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 ('Take an Artifact off the Pinned shelf') and scopes it to 'the user's own Artifacts library', which clearly frames it as the inverse of a pin operation. It does not name a sibling tool, so differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and the 'own library' scope, but there is no explicit when-to-use guidance, no mention of prerequisites (e.g., the artifact must currently be pinned), and no named alternative such as delete_artifact for removal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources