Veezee: LinkedIn people & company data for agents

Get Reddit posts by id, with optional discussion thread

reddit_get_post

Read-only

Fetch full post content for up to 100 Reddit posts by their t3_ ids in one call -- the follow-up loop after reddit_search or reddit_get_subreddit_posts. Costs 4 credits for up to 10 ids, +1 credit per further 10 ids; every post comes back with its full body text. With exactly ONE id you may set detail to 'full' for +4 credits to also get the discussion tree (comments flattened in tree order with depth, about 200 per page, with a comments_cursor to continue), or pass comment_id (a t1_ id, also +4 credits) to fetch one specific comment in its post context. Post ids come from the other Reddit tools or from reddit_resolve_url on a post URL. Not for discovering posts; search first, then batch-fetch here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	Discussion-tree order; only with detail 'full'.
`cursor`	No	comments_cursor from a previous detail='full' page.
`detail`	No	'full' adds the discussion tree; only valid with exactly one id, +4 credits.	concise
`post_ids`	Yes	1 to 100 post ids with the t3_ prefix, e.g. ["t3_1tbups6"].
`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
`comment_id`	No	A t1_ comment id to fetch in context; only valid with exactly one post id, +4 credits like detail 'full'.
`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.

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?

Annotations declare readOnlyHint and openWorldHint. The description elaborates on credit costs, pagination, caching behavior, freshness options with trial key limitations, and conditions for using detail and comment_id. No contradictions found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed and covers many nuances, but every sentence adds value. It is front-loaded with the main purpose and then provides necessary details. Slightly long but justified by complexity.

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 complexity (7 params, output schema exists), the description covers all states: multiple ids, single id with/without detail, comments cursor pagination, caching, and credit costs. It is complete for the agent to use the tool correctly.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning beyond schema: validity conditions for parameters (detail 'full' only with one id, sort only with detail 'full'), credit implications, caching behavior, and explanation of cursor usage.

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 it fetches full post content for up to 100 Reddit posts by t3_ ids, and optionally retrieves a discussion thread. It distinguishes from siblings by explicitly noting it is the follow-up after reddit_search or reddit_get_subreddit_posts and not for discovering posts.

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?

Provides explicit when to use (after search tools, batch fetch) and when not to use (not for discovering posts). Mentions alternatives like reddit_resolve_url for post ids, and details credit costs and conditions for different modes.

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?