Skip to main content
Glama

analyze_insight

Read-only

Assess subreddit discussion depth and sentiment to identify communities with substantive interactions.

Instructions

Measure a subreddit's discussion depth (insight): how substantive its comments are, plus a heuristic sentiment read. No creds needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoComment lookback window, e.g. 3d/7d3d
sampleNoComments to sample
subreddit_nameYesSubreddit name (without r/)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already provide readOnlyHint=true; description adds value by stating 'No creds needed' and explaining the heuristic sentiment read. Does not contradict annotations.

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?

Single informative sentence plus a separate statement, no wasted words. Front-loaded with key action and resource.

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?

With output schema present and annotations, the description covers purpose, auth requirement, and key behavior. Adequate for the tool's complexity.

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% with descriptions for all parameters. Description does not add extra meaning beyond schema; baseline 3 is appropriate.

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?

Description clearly states verb 'Measure' and resource 'subreddit's discussion depth', specifying what it measures (substance and sentiment) and distinguishes from siblings like 'analyze_subreddit' which might have different metrics.

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?

Implies usage via 'No creds needed' but lacks explicit guidance on when to use this tool over siblings like 'analyze_subreddit' or 'find_target_subreddits_tool'. No alternatives or exclusions listed.

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/latent-9/reddit-growth-mcp'

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