Skip to main content
Glama

screener_reddit_mentions

Screen Reddit mentions across stock tickers to track community interest and discussion trends. Returns detailed rows and summary statistics.

Instructions

Screen Reddit mentions across tickers. Returns rows with ticker, name, date, total_mentions, subreddits, plus a summary with aggregate stats (top_mentioned, subreddit_names, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reqYesScreener request with optional market/region.
Behavior2/5

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

No annotations provided; description does not disclose behavioral traits such as read-readiness, rate limits, or data staleness. It only states what is returned, missing safety or side-effect context.

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?

Two sentences with no wasted words: first states purpose, second lists output fields. Highly efficient and easy to parse.

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

Completeness3/5

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

Describes output rows and summary but does not explain how parameters like market/region affect behavior. For a nested-object screener, more context on filtering semantics would be helpful, but no output schema exists to compensate.

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 the description adds no extra meaning to parameters beyond schema descriptions. Baseline score 3 is appropriate as the description repeats output details but not parameter context.

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 'Screen Reddit mentions across tickers,' which is a specific verb and resource. It distinguishes from sibling 'reddit_mentions_by_ticker' by indicating cross-ticker screening vs. single-ticker retrieval.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs. alternatives like 'reddit_mentions_by_ticker'. The name implies screening across tickers but the description does not provide when-not or alternative tool references.

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/ahmetsbilgin/finbrain-mcp'

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