Skip to main content
Glama

list_job_files

List the output files a browser task wrote, including extracted data and a session.gif recording, returning each file's name and size by job id.

Instructions

List the output files a task wrote — extracted data + a session.gif recording. Returns name + size per file.

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": {
      "job_id": "<job_id>"
    },
    "name": "list_job_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id from run_task / create_task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the return shape (name and size per file) and that a session.gif recording is included, but says nothing about pagination, file retention/expiry, permissions, or whether missing files yield an empty list or an error.

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?

Two short sentences, front-loaded with the core action, with the return-value detail placed second. No filler or restated title.

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 one-parameter read tool with no output schema, the description covers both what is listed and what comes back (name plus size per file), which is the key gap output schemas normally fill. Minor omissions around empty results and file expiry keep it below a 5.

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 100% and the single job_id is already documented with its origin, so the baseline is 3. The description adds slight value by framing job_id as a task identifier whose files are being enumerated, reinforcing the producer relationship.

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 ('List') and resource ('output files a task wrote'), and enumerates the actual payload (extracted data plus a session.gif recording), so an agent can distinguish it from job-control siblings like get_job or cancel_job without opening a 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?

Usage context is implied rather than stated: the job_id description ties it to run_task / create_task, telling the agent this is the post-task retrieval step. It never says explicitly when not to use it or how it differs from get_job, which likely returns job status rather than files.

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