Skip to main content
Glama

GitHub download artifact

github_download_artifact
Read-only

Download and read the contents of a GitHub Actions artifact. Prefer the exact owner from github_list_repositories; 'repo' also accepts the combined 'owner/name' form. Downloads the artifact zip, extracts it, and returns the contents of text/JSON files inside. Use this to read Trivy vulnerability scan results (from 'ankra-security-scan' artifacts), test reports, or other CI/CD outputs. Get the artifact_id from github_list_artifacts first.

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": {
      "repo": "<repo>",
      "artifact_id": "<artifact_id>"
    },
    "name": "github_download_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name. Also accepts the combined 'owner/name' form.
ownerNoRepository owner (e.g. 'octocat'). Prefer the exact owner from a prior github_list_repositories call. May be omitted when the repository name is unambiguous in this organisation, or embedded in 'repo' as 'owner/name'.
artifact_idYesThe artifact ID. Get this from github_list_artifacts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, and the description goes well beyond that by disclosing the internal mechanism: it downloads the zip, extracts it, and returns the contents of text/JSON files inside. It stops short of noting limits such as binary-file handling, artifact size, or expiry, which matters since there is no output schema.

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?

Four short sentences ordered as purpose, parameter hint, mechanism, use cases, prerequisite — all front-loaded with nothing redundant. Every sentence contributes either routing or behavioural information.

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?

With no output schema, the description correctly takes on the burden of explaining what is returned (extracted text/JSON contents), which is the key missing piece. Remaining omissions are edge-case behaviour for non-text artifacts and size limits, which are minor for a read-only tool.

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% and the schema already documents the 'owner/name' form for repo, the owner omission rule, and that artifact_id comes from github_list_artifacts. The description largely restates those points rather than adding syntax, format, or fallback behaviour, so it earns only the baseline.

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?

States a specific verb and resource ('Download and read the contents of a GitHub Actions artifact') and implicitly separates itself from github_list_artifacts and github_get_job_logs by naming the download/extract behaviour. An agent can tell what it produces without opening the schema.

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?

Gives concrete use cases ('Trivy vulnerability scan results from ankra-security-scan artifacts, test reports, or other CI/CD outputs') and an explicit prerequisite chain: get artifact_id from github_list_artifacts, prefer the exact owner from github_list_repositories. The only gap is that it never states a when-not-to-use condition, but the routing is otherwise unambiguous.

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.