Mercari MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsC | Search Mercari listings by keyword, category, and price range |
| get_listing_detailsB | Get detailed information about a specific Mercari listing |
| get_my_listingsA | Get listings the authenticated user is currently selling |
| create_listingB | Create a new listing on Mercari |
| get_purchasesA | View purchase history for the authenticated user |
| get_salesA | View sales history for the authenticated user |
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 6 tools
Each tool targets a distinct action: viewing own listings, purchases, sales, searching, getting details, and creating listings. No overlap in purpose.
All tools follow a consistent verb_noun pattern (e.g., get_my_listings, search_listings, create_listing), making the set predictable.
With 6 tools covering core marketplace operations (search, view, create), the count is well-scoped and not excessive.
Missing update and delete for listings, which are common lifecycle operations. The set covers creation and reading but not full CRUD.