Skip to main content
Glama

Get task artifacts

task_artifacts

List a finished task's artifacts (video.mp4, before.png/after.png screenshots, trace.tar.gz, stdout.log) with download URLs valid for 15 minutes. Pass download= to fetch one: screenshots come back as images, the log as text.

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": "task_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
downloadNoArtifact id (art_…) or file name to fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that URLs expire after 15 minutes and that screenshots return as images while the log returns as text, but it omits permissions, failure behavior for unfinished tasks, pagination, and size 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?

The description is two tight sentences, front-loaded with the list operation and followed by the fetch behavior. Every sentence adds useful information without repetition.

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 two-parameter read tool with no output schema, the description covers artifact types, URL expiry, download behavior, and return formats well. Minor gaps remain around error cases and task_id format, but the core invocation needs are addressed.

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 50%, and the description compensates by explaining the download parameter as an artifact id or file name and describing the different return formats. The required task_id is only implicitly defined as the finished task whose artifacts are listed.

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?

The description states a specific verb and resource: list a finished task's artifacts, with concrete examples like video.mp4, screenshots, trace.tar.gz, and stdout.log. It clearly distinguishes artifacts from task status by focusing on downloadable outputs, though it does not explicitly name sibling tools such as task_status.

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 explains when to omit download (to list artifacts) and when to pass download=<artifact id or file name> (to fetch one). It also scopes usage to finished tasks, but does not state exclusions or compare to task_status.

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