Skip to main content
Glama

GitHub list artifacts

github_list_artifacts
Read-only

List GitHub Actions artifacts for a repository. Prefer the exact owner from github_list_repositories; 'repo' also accepts the combined 'owner/name' form. Returns artifact names, sizes, creation dates, and expiry status. Use this to find build outputs like Trivy security scan results (artifact name 'ankra-security-scan'), test reports, coverage data, or any other CI/CD artifacts. You can filter by artifact name.

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>"
    },
    "name": "github_list_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilter artifacts by exact name (e.g. 'ankra-security-scan'). If not provided, returns all recent artifacts.
repoYesRepository name. Also accepts the combined 'owner/name' form.
limitNoMaximum number of artifacts to return (max 30).
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'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint=true annotation already tells the agent this is a safe read, so the bar is lower, and the description still adds useful behavior: the returned fields, that filtering by exact artifact name is possible, and that omitting the name returns all recent artifacts. It does not cover ordering, pagination, or whether artifacts from deleted runs appear, which keeps it short of a 5.

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 tight sentences, front-loaded with purpose, then the owner/repo addressing rule, then return fields, then use cases. Every sentence carries distinct information and nothing is repeated from the schema verbatim.

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 compensates by enumerating the returned fields and the default all-recent behavior, which is enough to call the tool correctly. Minor gaps remain around result ordering and how the agent should proceed to actually retrieve an artifact's bytes, which is presumably a sibling tool's job.

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 description coverage is 100%, so all four parameters are already documented, including the 'owner/name' form for 'repo' and the max-30 limit. The description's only genuine addition is the cross-tool hint to take the owner from github_list_repositories, which the schema also states; otherwise it largely restates the schema, so baseline 3 applies.

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 opening sentence names a specific verb and resource ('List GitHub Actions artifacts for a repository'), which cleanly separates it from siblings like github_download_artifact, github_list_workflow_runs, and github_get_workflow_run_jobs. It goes further by naming what is returned (names, sizes, creation dates, expiry status), so an agent knows the shape of the result 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 Guidelines4/5

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

It gives concrete use cases (Trivy security scan results under 'ankra-security-scan', test reports, coverage data) and a routing hint to prefer the exact owner from github_list_repositories. It does not explicitly say when to switch to github_download_artifact for fetching an artifact's contents, nor when to use workflow-run tools instead, so the alternative-selection guidance is clear but not exhaustive.

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.