Skip to main content
Glama

hf_job_list

Lists Hugging Face jobs, showing running and billing jobs by default; set include_finished to true to also view completed jobs.

Instructions

List your Hugging Face jobs. By default only those running (and billing) right now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hf_job_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_finishedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals the default filter (running jobs only) and the billing implication, but omits pagination, ordering, scope of 'your' (token/account), and any auth or rate-limit notes.

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?

Two short sentences, front-loaded with the core action and followed by the key default behavior. No filler, though the parenthetical '(and billing)' is slightly informal phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter list tool with an output schema present, the description covers the essentials of what it does and its default scope. Gaps remain around result ordering, pagination, and which account/namespace the listing applies to.

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 0%, so the description must compensate. The default-behavior sentence implicitly explains include_finished: the default excludes finished jobs, so setting it true broadens the result set. That is meaningful, but it is inferential rather than a stated mapping and leaves the flag itself unnamed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List your Hugging Face jobs'), which is clearly distinguishable from siblings like hf_job_cancel and hf_job_launch by virtue of being a read/list operation. It does not, however, explicitly contrast itself with alternatives such as hf_job_cancel, so it stops short of the top band.

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

Usage Guidelines3/5

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

The clause 'By default only those running (and billing) right now' implies the intended use case (monitoring active jobs), but there is no explicit when-to-use vs when-not guidance and no named alternative for retrieving historical or finished jobs.

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