Goofish MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOFISH_HEADLESS | No | Set to '1' to run in headless mode. Default: non-headless | |
| GOOFISH_PROFILE_DIR | No | Path to the browser profile directory. Default: ./.profiles/goofish |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_itemsB | Search Goofish/Xianyu items by keyword using a logged-in Playwright browser context. Example queries: iphone 15 pro, sony a7, dyson v12. |
| get_item_detailB | Get Goofish/Xianyu item detail by item_id or URL. |
| monitor_keywordC | Return a normalized Goofish/Xianyu keyword snapshot for monitoring. |
| publish_itemB | Publish a new Goofish/Xianyu second-hand item listing. |
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 4 tools
Each tool has a clearly distinct purpose: one for getting item details, one for setting up keyword monitoring, one for publishing items, and one for searching. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (get_item_detail, monitor_keyword, publish_item, search_items), making them predictable and easy to understand.
With 4 tools covering search, detail retrieval, publishing, and monitoring, the set is well-scoped for its domain without being excessive or insufficient.
While the server covers search, detail, publish, and monitoring, it lacks update and delete capabilities, leaving a notable gap in the full lifecycle of item management.