trendforge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRENDFORGE_HOST | No | Override the TrendForge host (e.g. for a staging build). | https://trendforgeapp.com |
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 |
|---|---|
| list_opportunitiesA | List the top YouTube gaming opportunities right now, ranked by TrendForge's opportunity score (0.4Demand + 0.35Supply + 0.25*Timing, each 0-100, higher = better). Use this when a creator asks what to play/record, or which games have an open content gap. Higher opportunity = demand is real but creator supply is still thin. |
| get_gameA | Get the full breakdown for one game: Demand/Supply/Timing scores, confidence, risk flags, a one-line reason it ranks, AI-generated video ideas (title + angle + why-now), and 3 related games. Needs a slug — get it from list_opportunities first, or pass a slug you know. |
| check_topicA | Run a live YouTube shelf check on any game, topic, or query: returns opportunity verdict, demand, competition pressure, big-channel dominance, Shorts mix, exact-title collisions, fit for a channel size, suggested angles, and the top recent videos returned. Heavier call (hits YouTube API) — use for a specific idea the creator is seriously considering, not for browsing. |
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
Each tool serves a distinct purpose: list_opportunities for browsing ranked opportunities, get_game for deep-diving into a specific game, and check_topic for live YouTube checks on arbitrary queries. No overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern (list_, get_, check_), using lowercase with underscores. The naming convention is uniform and intuitive, matching the action each tool performs.
The server has 3 tools, which is well-scoped for its niche purpose of YouTube gaming opportunity analysis. Each tool is essential and earns its place, covering browsing, detail retrieval, and live validation without redundancy.
The tool surface fully covers the domain's needs: list_opportunities provides the overview, get_game offers granular data for one game, and check_topic enables ad-hoc validation of any idea. No obvious gaps exist for a read-only analytics service.