Skip to main content
Glama
ywleeo
by ywleeo

reddit_search

Read-onlyIdempotent

Search Reddit posts by keyword and get normalized post metadata with direct links for easy access.

Instructions

Search Reddit posts and return normalized post metadata and links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNorelevance
limitNo
keywordYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortYes
itemsYes
keywordYes
Behavior3/5

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

Annotations already cover safety with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that results are 'normalized post metadata and links,' giving some output behavior context, but no details on pagination, sorting defaults, or rate limits. With annotations covering the safety profile, a neutral score is appropriate.

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 a single concise sentence that immediately states the tool's purpose and output. No wasted words or repetition of structured information.

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?

An output schema is present, so return values need not be explained. However, the description is very brief and leaves parameter usage unspecified, especially given the input schema lacks property descriptions. It is minimally viable for a simple search tool but not richly complete.

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

Parameters1/5

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

Schema description coverage is 0% per context signals, and the tool description does not elaborate on the 'keyword,' 'limit,' or 'sort' parameters. The description adds no meaning beyond the schema's property titles and defaults, so it fails to compensate for the lack of schema descriptions.

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 the tool's action: 'Search Reddit posts' and the output: 'return normalized post metadata and links.' It distinguishes from sibling tools like reddit_post (which likely fetches a specific post) and other site-specific search tools (zhihu_search, xhs_search).

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 clear context: it is for searching Reddit posts. However, it does not explicitly mention when not to use it or point to alternatives (e.g., reddit_post for a specific post), so it misses the highest bar for usage guidance.

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/ywleeo/browser-mcp'

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