chrome-downloader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chrome_download_statusA | 查本机下载桥是否可用、扩展有没有连上、出站熔断状态。排查第一步就敲它。插件冷启动最长约 30 秒（Chrome 扩展后台定时器官方下限），任务没动静先看这里的 extensionConnected。 |
| chrome_downloadA | 提交一个或一批 URL 给浏览器下载。服务端不取任何字节，只把任务交给扩展。注意：插件冷启动最长约 30 秒才醒（官方定时器下限），所以提交后进度不立刻动是正常的；要等结果请带 wait=true 或改用 chrome_download_wait。 |
| chrome_download_listA | 列出账本里的下载任务（含状态/进度/字节数）。账本很大时本工具会截断到单行 8192 字节以内并标 truncated=true，届时请用 jobId 精确查（chrome_download_progress）。插件冷启动最长约 30 秒。 |
| chrome_download_progressA | 看一个 jobId 的实时进度与网速。插件冷启动最长约 30 秒，刚提交的任务数字不动属正常，别重复提交。 |
| chrome_download_waitA | 阻塞等到指定 jobId 全部进入终态（COMPLETE/FAILED/CANCELLED）或超时。超时上限 600 秒；插件冷启动最长约 30 秒，把 timeout 压太小会误判成没下完。 |
| chrome_download_pauseB | 暂停一个正在下的任务。插件冷启动最长约 30 秒；暂停是发给扩展的指令，扩展睡着时这条会排队到它醒来。 |
| chrome_download_resumeB | 继续一个被暂停/中断的任务（能续传则 Range 续传，不能则整单重头下，重头下会标 restarted=true）。插件冷启动最长约 30 秒。 |
| chrome_download_cancelB | 取消一个任务（不可逆；要重下请新提交）。插件冷启动最长约 30 秒。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a distinct role: status checks bridge/extension health, list enumerates tasks, download submits URLs, progress reports one job, wait blocks until terminal state, and pause/resume/cancel control a specific job. The boundaries are clear and descriptions help reinforce them, so misselection is unlikely.
All tools use snake_case with a consistent chrome_download_ prefix, and suffixes clearly indicate the operation (status, list, progress, wait, pause, resume, cancel). The base chrome_download is the submit action, which fits the same predictable pattern.
Eight tools are well-scoped for a browser download bridge, covering health, submission, monitoring, waiting, and lifecycle control without redundant or missing operations. The count is neither bloated nor too thin for the domain.
The core download lifecycle is well covered: submit, list, inspect progress, wait, pause, resume, cancel, and check bridge health. Minor gaps exist around ledger cleanup or bulk operations, but agents can work around those for typical use.