Japan Used Camera Market MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token (Apify Console → Settings → API & Integrations). Runs are billed to your Apify account. | |
| APIFY_API_BASE_URL | No | Overrides the Apify API base URL (used by the tests). |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Search current used camera / lens listings at Japanese shops (Fujiya Camera, Sanpou Camera, Naniwa new arrivals, Hard Off Off Mall). Returns title, brand, normalized condition grade, price in JPY and USD, stock status and URL. Takes ~15–60 s. |
| price_statsA | Per-model price summary of in-stock listings right now: count and min / median / max (JPY and USD), broken down by shop and by normalized condition grade, plus the cheapest listing. Use keywords to stay fast (~1–4 min). |
| price_historyA | Daily min / median / max / count per model, by shop and condition grade, from stored daily snapshots of the shops (Fujiya, Sanpou and Naniwa; collected since 2026-11-05, so the first month is short). No crawling — returns in seconds. Needs keywords, brands or models. |
| start_monitorA | Creates, in the user's own Apify account, a saved Task running this Actor in monitor mode and a Schedule for it (hourly by default), then starts the first run to record the baseline. Later runs emit only changes (NEW / PRICE_DROP / PRICE_UP / SOLD_OUT) and can POST them to a Slack / Discord / n8n webhook. This creates resources and recurring runs that use the user's Apify credit — confirm with the user first. |
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 targets a distinct mode of access: live search, current aggregate stats, stored historical snapshots, and automated monitoring setup. The only potential overlap is price_stats vs price_history, but the descriptions cleanly separate 'in-stock right now' from 'stored daily snapshots over time'. No two tools appear interchangeable.
All names use snake_case, which is consistent, but the verb pattern is mixed: search_listings and start_monitor are verb_noun while price_stats and price_history are noun-only. Still highly readable and predictable enough for an agent to infer purpose.
Four tools is on the lean side but each maps to a genuinely different capability (search, aggregate, history, monitoring), so nothing feels redundant. Marginal thinness aside, the surface is well-scoped for a niche market-data server.
The find-analyze-track lifecycle is covered: search live listings, summarize current prices, query historical trends, and set up ongoing monitoring. Minor gaps exist (no single-listing detail fetch, no way to enumerate supported shops/brands/models, no monitor management/edit), but agents can work around these via keyword search and start_monitor's parameters.