Skip to main content
Glama

list_artifacts

Read-onlyIdempotent

Retrieves artifacts attached to a task, returning download paths and any human-only links needed to access each file.

Instructions

List artifacts attached to a task. Each carries download_path; a browser_only_url block, when present, is a human-only page. Downloading an artifact is two GETs. Step 1: GET /api/v1/artifacts//download with header X-Agent-Key: -> 200 JSON {"url": ""}. Step 2: GET that url with NO headers -> 200, the file bytes. Pitfalls: on step 1 only X-Agent-Key is accepted (X-API-Key and Authorization: Bearer give 401); on step 2 any extra header, Authorization in particular, breaks the presigned signature (400). The artifact's download_path is step 1's path. browser_only_url is a human page and answers 401 to an agent key by design.

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": {
      "task_id": "<task_id>"
    },
    "name": "list_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description goes well beyond them: exact auth header acceptance on step 1 (only X-Agent-Key; X-API-Key and Bearer yield 401), the header-free requirement on step 2 (extra headers, especially Authorization, break the presigned signature with 400), and the human-only nature of browser_only_url that returns 401 by design. These are precisely the failure modes an agent would otherwise hit blind.

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?

Purpose is front-loaded in the first sentence, then a numbered two-step recipe and a compact pitfalls sentence. Every sentence carries actionable detail, but the download procedure is arguably out of scope for a list tool and inflates length relative to the one-param surface.

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?

With no output schema, the description must explain what comes back, and it does: each item has download_path plus an optional browser_only_url. It also supplies the full follow-on download protocol and its error semantics, leaving no ambiguity about how to actually retrieve the bytes.

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% for the single task_id parameter, so the baseline is 3 even though the description adds nothing about it. The description's real semantic contribution is to the response fields (download_path, browser_only_url), which is helpful but not input-parameter guidance.

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?

Opens with a specific verb+resource+scope: "List artifacts attached to a task." This is clearly distinct from the singular sibling get_artifact, though it never names that sibling explicitly to reinforce the boundary. The rest of the description pivots to download mechanics rather than listing, which slightly dilutes the stated purpose.

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?

It gives concrete operational context: list for a task, then use download_path for the two-GET download flow, and ignore browser_only_url for agent use. There is no explicit statement of when to prefer this over get_artifact or of any exclusion, so it stops short of full routing guidance.

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