Skip to main content
Glama

social-momentum

Query Reddit, Hacker News, and GitHub in parallel for any topic. Get a composite momentum score (0–100) and raw results to determine if a topic is gaining traction.

Instructions

Cross-platform social momentum for any topic. Queries Reddit (recent top posts), Hacker News (recent stories), and GitHub (active repos) in parallel and returns a composite momentum score (0–100) plus raw results from each platform. Single call replaces three separate searches. Use before committing to research, writing, or trading: 'is this topic gaining traction right now?' No API keys required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoTopic or entity to query across all platforms. E.g. 'ethereum staking', 'LLM agents', 'Anthropic', 'DeFi yields'.
window_hoursNoLookback window in hours (default 24, min 1, max 168 = 7 days). Shorter windows are more noise-sensitive; 24–72h gives the most stable signal.
reddit_subredditsNoRestrict Reddit search to specific subreddits (e.g. ['bitcoin', 'ethereum', 'CryptoCurrency']). Omit to search all Reddit.
reddit_limitNoMax Reddit posts to return (1–20, default 10).
hn_limitNoMax HN stories to return (1–20, default 10).
github_limitNoMax GitHub repos to return (1–20, default 10).
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses parallel queries, composite score range, and raw results. However, it omits potential behavioral traits like rate limits, data freshness, or side effects. It does state 'No API keys required,' which is useful but not exhaustive.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the core action, and every sentence provides essential information. No wasted words.

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

Completeness5/5

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

Given no annotations and no output schema, the description sufficiently explains return values (composite score and raw results), parallel execution, and typical use case. For a tool with 6 optional parameters, it covers what a user needs to know to invoke it correctly.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds overall context but does not enrich parameter semantics beyond what the schema already provides. The schema descriptions themselves are thorough (e.g., window_hours explains default, range, and sensitivity), so additional description value is marginal.

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 clearly states it queries three platforms in parallel, returns a composite score and raw results, and explicitly distinguishes from sibling tools by claiming it replaces three separate searches. The verb 'queries' and resource 'social momentum' are specific and actionable.

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

Usage Guidelines4/5

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

Provides explicit usage context: 'Use before committing to research, writing, or trading' and gives a quintessential question. Mentions it replaces three separate searches, implying when to use this over individual platform tools. Does not explicitly state when not to use, but the guidance is clear and helpful.

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/thebrierfox/the-stall'

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