Veezee: LinkedIn people & company data for agents

Get a subreddit's posts

reddit_get_subreddit_posts

Read-only

Fetch one page of posts from a single subreddit, the community-monitoring primitive. subreddit_name is the name without the r/ prefix. sort defaults to the subreddit's own front-page order (best); use sort=new for monitoring. sort=top and controversial need a range, but the window is currently not applied upstream on this feed: top returns the subreddit's all-time top posts whatever range says (time-windowed tops are a known gap here; reddit_search's range DOES work for keyword queries). Costs 4 credits per page; a cursor page is a NEW call priced the same way. Reddit splices about one promoted ad into every feed page; these are dropped by default, so set include_promoted=true only when ads ARE the data you want (ad intelligence, who targets this community) -- kept ads carry is_promoted=true. Returns post summaries (title, author, upvotes, comment_count, created_at, permalink, id) with a cursor for older posts; bodies and discussions come from reddit_get_post with the returned ids. For keyword search across all of Reddit use reddit_search; this tool takes no query.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	Defaults to the subreddit's front-page order.
`range`	No	Required with sort=top or controversial, but currently not applied upstream on this feed (results are all-time).
`cursor`	No	Cursor from a previous page for older posts.
`freshness`	No	recent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it.	recent
`max_credits`	No	Spend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling.
`subreddit_name`	Yes	Subreddit name without the r/ prefix, e.g. 'selfhosted'.
`include_promoted`	No	Keep the promoted ads Reddit splices into the feed (marked is_promoted). Default drops them.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`usage`	Yes
`common`	Yes
`entity`	Yes
`platform`	Yes
`freshness`	Yes
`data_as_of`	Yes
`canonical_url`	Yes
`schema_version`	Yes
`platform_fields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint/openWorldHint annotations by disclosing credit costs, the fact that cursor pages are new calls, the ad-splicing behavior and default dropping of promoted posts, the range-window bug, and the return shape. No contradiction with annotations exists.

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 dense but every sentence earns its place, front-loading the core purpose and then layering caveats and alternatives in a logical order. The caveats about range, credits, and ads are necessary rather than filler.

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 the tool's complexity and output schema, the description is thorough: it names the returned fields, explains the cursor for pagination, points to the companion tool for bodies/discussions, and covers the main edge cases. Nothing required to call this tool correctly is missing.

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

Parameters4/5

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

Even though schema coverage is 100%, the description adds real semantic value: it explains sort=new for monitoring, warns that range is not currently applied upstream for top/controversial, and clarifies include_promoted's purpose. This is above the baseline, though not all parameters receive equal narrative treatment.

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 opens with a precise verb and resource: 'Fetch one page of posts from a single subreddit.' It also distinguishes itself from sibling tools by stating this tool takes no query, that bodies/discussions come from reddit_get_post, and that keyword search should use reddit_search.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: use sort=new for monitoring, use reddit_search for keyword queries, and use reddit_get_post for post bodies. It also warns about the range caveat with sort=top and when to set include_promoted=true, making selection and invocation conditions clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Veezee: LinkedIn people & company data for agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?