Skip to main content
Glama

get_viral_social_gaps

Identify 5 time-sensitive viral trend gaps for TikTok challenges, HBO premieres, and short-window consumer builds. Peak windows measured in days or weeks.

Instructions

SPECIALIZED TOOL — only use when the user explicitly asks for VIRAL, SOCIAL, TIKTOK, CONSUMER, TREND-BASED, or SHORT-WINDOW build opportunities. Returns 5 time-sensitive consumer/viral trend gaps (TikTok challenges, HBO premieres, viral formats) with peak windows measured in days or weeks. DO NOT call this tool for general 'find me ideas' or 'what should I build' queries — those should use search_gaps which returns serious validated business opportunities across 7 industries. Only call this when the user specifically mentions viral, social, trend, TikTok, Instagram, or consumer-facing short-window builds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:171-179 (registration)
    Tool registration in the TOOLS array with name, description, and inputSchema (no parameters required).
    {
      name: "get_viral_social_gaps",
      description:
        "SPECIALIZED TOOL — only use when the user explicitly asks for VIRAL, SOCIAL, TIKTOK, CONSUMER, TREND-BASED, or SHORT-WINDOW build opportunities. Returns 5 time-sensitive consumer/viral trend gaps (TikTok challenges, HBO premieres, viral formats) with peak windows measured in days or weeks. DO NOT call this tool for general 'find me ideas' or 'what should I build' queries — those should use `search_gaps` which returns serious validated business opportunities across 7 industries. Only call this when the user specifically mentions viral, social, trend, TikTok, Instagram, or consumer-facing short-window builds.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Handler logic in the CallToolRequestSchema switch statement: returns the TRENDS constant (loaded from data/trends.json) along with a note explaining these are viral consumer trends.
    case "get_viral_social_gaps":
      payload = {
        viral_social_gaps: TRENDS,
        _note:
          "These are VIRAL CONSUMER trends with short peak windows (days to weeks) — TikTok, HBO, social formats. For serious B2B / validated business opportunities, use the `search_gaps` tool which covers 474 gaps across 7 industries. Updated weekly at thevibepreneur.com.",
      };
  • Data loading: TRENDS is loaded from data/trends.json at startup and returned as viral_social_gaps by the handler.
    const TRENDS = JSON.parse(readFileSync(join(DATA_DIR, "trends.json"), "utf8"));
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description bears full responsibility. It discloses output structure (5 gaps, peak windows in days/weeks) and implies read-only behavior. Lacks explicit statement of non-destructive nature or permissions but is sufficient for safe use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with 'SPECIALIZED TOOL' and bold usage restrictions. While somewhat lengthy, every sentence adds value. Minor redundancy in listing trigger words could be trimmed, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, description adequately covers what the tool does, when to use it, and what it returns (5 gaps). Missing explicit output structure for agent processing, but sufficient for invocation decision.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has zero parameters, so baseline is 4 per rubric. No parameter explanation needed; description doesn't cover parameters because there are none.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool returns 'time-sensitive consumer/viral trend gaps' and specifies exact trigger conditions (TikTok challenges, HBO premieres, viral formats). It clearly distinguishes from sibling tool `search_gaps` by contrasting the scope (viral/social vs serious business opportunities).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use ('only use when user asks for VIRAL...') and when not to ('DO NOT call for general queries'), and names the alternative tool (`search_gaps`) with its purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thevibepreneur/gapbase-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server