Skip to main content
Glama
ywleeo
by ywleeo

reddit_post

Read-onlyIdempotent

Fetch a Reddit post and its comments directly from a URL using your active Chrome session. Handles dynamic and login-required Reddit pages. Optionally set a maximum comment count.

Instructions

Read one Reddit post and a bounded set of comments rendered on its page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
max_commentsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
bodyYes
scoreYes
titleYes
authorYes
post_idYes
commentsYes
media_urlYes
post_typeYes
subredditYes
published_atYes
comment_countYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context by noting comments are 'bounded', implying the max_comments parameter limits the output size. This goes beyond what annotations say.

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 front-loads the core action and resource. Every word earns its place with no redundancy or filler.

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?

Given the tool's simplicity, the description is adequate but leaves gaps: it does not specify the expected URL format, the nature of the 'bounded set' (e.g., whether max_comments is exact or cap), or how comments are ordered. The output schema and annotations fill some context, but the description could be more complete for a new agent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for param semantics. It hints at the bounded comments but does not explain the url format or how max_comments controls the bounds. The parameter names are self-explanatory but the description adds little meaningful detail.

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 uses the specific verb 'Read' and clearly identifies the resource as 'one Reddit post' plus 'a bounded set of comments'. This distinguishes it from search tools like reddit_search and browser navigation tools.

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

Usage Guidelines2/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 versus alternatives (e.g., reddit_search or browser_read). The usage is implied by the description but no exclusions or alternative scenarios are mentioned.

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