depot-mcp

Overview Schema Source Related Servers Discussions Admin

Get a signed download URL for one Depot CI artifact

depot_get_ci_artifact_url

Read-onlyIdempotent

Obtain a short-lived signed download URL for a specific Depot CI artifact by ID, then fetch the file immediately. Ideal for retrieving test reports, screenshots, or binaries for analysis.

Instructions

Mint a short-lived signed download URL for one Depot CI artifact, by artifact id.

Use this when you already know which artifact you want (from depot_list_ci_artifacts) and need to fetch it: a JUnit report to read the failing test names, a screenshot from a browser test, a built binary. Download it with curl or fetch as soon as you have the URL, since Depot signs it for minutes, not hours.

The URL is a bearer capability. Anyone holding it can download the artifact until it expires, so treat it like a credential: use it immediately and never write it anywhere durable (commit messages, issues, chat, files). This tool returns the URL only; it does not download the artifact or read its contents, and it cannot upload, replace, or delete anything.

To see what a run produced, or to get URLs for several artifacts in one call, use depot_list_ci_artifacts (with withDownloadUrl=true) instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`artifactId`	Yes	The artifact id, as returned by depot_list_ci_artifacts.

Output Schema

TableJSON Schema

Name	Required	Description
`warning`	Yes	Handling instructions: the URL is a bearer capability.
`expiresAt`	No	When the signature expires, when the URL says so.
`artifactId`	Yes
`downloadUrl`	Yes	Signed HTTPS URL. Short-lived; do not store it.
`expiresInSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.1Sep 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the URL expires in minutes, is a bearer capability, should not be persisted, returns only the URL, and cannot upload, replace, or delete artifacts.

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?

Well structured with clear paragraphs, but repeats the short-lived signed URL idea and the download-with-curl instruction, making it slightly more verbose than necessary.

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 single-parameter read-only tool, it fully covers how to use it, what it returns, its security implications, and when to use the sibling listing tool instead.

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?

The sole parameter artifactId has a schema description that already covers its meaning and provenance; the tool description adds minimal extra parameter-level detail beyond that.

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?

Clearly states it mints a short-lived signed download URL for one Depot CI artifact by artifact ID, and distinguishes itself from depot_list_ci_artifacts as the targeted single-artifact retrieval tool.

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

Usage Guidelines5/5

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

Explicitly says to use this when you already know which artifact you need, and names depot_list_ci_artifacts with withDownloadUrl=true as the alternative for listing artifacts or getting multiple URLs.

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