Skip to main content
Glama

List Experiment Files

encode_list_files
Read-onlyIdempotent

List files from an ENCODE experiment by accession, filtering by format, output type, or assembly. Returns file metadata including download URLs.

Instructions

List all files for a specific ENCODE experiment, with optional filters.

Examples:

  • All BED files: experiment_accession="ENCSR133RZO", file_format="bed"

  • FASTQs only: experiment_accession="ENCSR133RZO", file_format="fastq"

  • Signal tracks: experiment_accession="ENCSR133RZO", output_category="signal"

  • Default/recommended files: preferred_default=True

  • Peaks from GRCh38: file_format="bed", output_type="IDR thresholded peaks", assembly="GRCh38"

Common file_format values: "fastq", "bam", "bed", "bigWig", "bigBed", "tsv", "hic"

Common output_type values: "reads", "alignments", "signal of unique reads", "signal of all reads", "fold change over control", "IDR thresholded peaks", "pseudoreplicated peaks", "replicated peaks", "gene quantifications", "transcript quantifications", "contact matrix"

WHEN TO USE: Use to browse files within a known experiment. Use encode_search_files instead to find files across experiments. RELATED TOOLS: encode_search_files, encode_get_file_info, encode_download_files

Args: experiment_accession: ENCODE experiment accession (e.g., "ENCSR133RZO") file_format: Filter by format ("fastq", "bam", "bed", "bigWig", "bigBed", etc.) file_type: Filter by specific type ("bed narrowPeak", "bed broadPeak", etc.) output_type: Filter by output type ("reads", "peaks", "signal", etc.) output_category: Filter by category ("raw data", "alignment", "signal", "annotation") assembly: Filter by genome assembly ("GRCh38", "hg19", "mm10") status: Filter by status ("released", "archived", "in progress") preferred_default: If True, return only default/recommended files limit: Max files to return (default 200)

Returns: JSON list of files with accession, format, size, download URL, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
experiment_accessionYes
file_formatNo
file_typeNo
output_typeNo
output_categoryNo
assemblyNo
statusNo
preferred_defaultNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description confirms it is a listing operation and mentions the return format, but does not add significant behavioral context beyond what annotations provide. No contradictions.

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 well-structured with a concise summary, followed by examples, parameter list, usage guidance, and related tools. It is front-loaded and every section is informative and 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?

Given the complexity (9 parameters, 1 required) and the presence of an output schema, the description adequately covers functionality, examples, common values, and return type. It is complete for an agent to correctly select and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema_description_coverage is 0%, so the description bears full responsibility. It provides detailed explanations for all 9 parameters, including common values and examples (e.g., file_format: 'Common file_format values: "fastq", "bam", "bed", ...'). This adds substantial meaning beyond the bare schema.

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 description clearly states the tool lists files for a specific ENCODE experiment with optional filters. It distinguishes from siblings like encode_search_files (which searches across experiments) and encode_get_file_info (which gets info for a single file).

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?

The description explicitly states 'WHEN TO USE: Use to browse files within a known experiment. Use encode_search_files instead to find files across experiments.' It also provides a list of related tools, offering clear guidance on when to use this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ammawla/encode-toolkit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server