Skip to main content
Glama

Artifact Manage Tool

artifact_manage
Destructive

List, retrieve, and download artifacts from experiments, crew executions, and project runs. Access metadata, inline content, or signed download URLs for versions.

Instructions

Read-only access to artifacts produced by experiments, crew executions, and project runs (code, documents, data, media). Each artifact has 1..N ArtifactVersion entries; version defaults to latest when omitted. download returns a signed URL valid for ~5 minutes; content returns the body inline (base64 for binary MIMEs).

Actions:

  • list (read) — exactly one of: experiment_id, crew_execution_id, project_run_id; optional limit.

  • get (read) — artifact_id. Metadata only (size, mime, version count, created_by AiRun id).

  • content (read) — artifact_id; optional version. Returns raw or base64 body.

  • download (read) — artifact_id; optional version. Returns short-lived signed URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list, get, content, download
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
experiment_idNoFilter by experiment UUID
crew_execution_idNoFilter by crew execution UUID
project_run_idNoFilter by project run UUID
limitNoMax results (default 20, max 100)
artifact_idYesThe artifact UUID
versionNoSpecific version number (default: latest)
include_contentNoInclude full content in response (default true). Set false for metadata only.
Behavior1/5

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

Annotations declare destructiveHint: true, but the description asserts 'Read-only access.' This is a direct contradiction: read-only tools should not have destructiveHint. The description fails to disclose why it is marked destructive, misleading the agent about potential side effects.

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?

Description is front-loaded with purpose, followed by a bulleted list of actions with precise details. Every sentence is informative; no fluff or redundancy.

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

Completeness3/5

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

Despite strong parameter documentation, the glaring contradiction between 'read-only' description and destructiveHint annotation undermines completeness. The agent lacks understanding of whether this tool can cause harm. Otherwise, the description would be complete.

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

Parameters5/5

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

Schema has 100% coverage, but the description adds significant value: explains default version behavior, signed URL expiry (~5 min), content encoding for binary types, and clarifies each action's output. This goes well beyond the schema definitions.

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?

The description clearly states 'Read-only access to artifacts' and enumerates four specific read actions (list, get, content, download). It effectively communicates the tool's purpose and distinguishes it from other management tools that likely support write operations.

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?

The description implies usage scenarios: retrieving artifacts and their versions. It provides context for when to use this tool (read-only operations) but does not explicitly state when not to use it or mention alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/escapeboy/agent-fleet-o'

If you have feedback or need assistance with the MCP directory API, please join our Discord server