mcp-sales-intel
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_gigsB | Scrape live Fiverr search results for a query and return gig cards with title, seller, rating, review count, entry price and URL. Use this to scout what sellers are actually offering and charging. |
| analyse_marketA | Take raw Fiverr search-page markdown (as a string) and compute pricing bands, review-count distribution and an 'open market' verdict — i.e. how reachable a new seller is. Use for competitive analysis without re-scraping. |
| price_gigB | Given a set of gigs (or a market query), recommend a three-tier Basic/Standard/Premium package ladder with prices anchored to observed medians. |
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 3 tools
The three tools target clearly distinct actions: scraping live gigs, analyzing supplied market markdown, and generating a pricing ladder. Their descriptions make boundaries explicit, so an agent should not confuse list_gigs with analyse_market or price_gig.
All names follow a consistent snake_case verb_noun pattern: list_gigs, analyse_market, price_gig. The convention is predictable and readable throughout.
Three tools cover the core scrape-analyze-price workflow without redundancy, which is well-scoped for a niche sales-intel server. It is slightly lean, but each tool earns its place.
The surface covers scraping, analysis, and pricing, but there is a notable gap: analyse_market requires raw Fiverr search-page markdown while list_gigs only returns structured gig cards, leaving no direct tool path to obtain that input. Additional gaps include seller-level detail and historical tracking, though the main workflow is partially covered.