Skip to main content
Glama

get_post

Read-onlyIdempotent

Retrieve a Reddit post with its comment tree from live or archive sources, letting you control comment sort, depth, and limit for thread analysis.

Instructions

Get a post with its comment tree.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post": "<post>"
    },
    "name": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesPost id (abc123 or t3_abc123) or post URL
sourceNoData source. 'auto' tries live reddit.com (if a session cookie is configured) and falls back to the Arctic Shift archive; 'live' or 'archive' forces one.auto
comment_sortNoComment orderbest
comment_depthNoReply levels to show; deeper ones are collapsed
comment_limitNoMax comments to load

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact - the result includes the comment tree - but says nothing about the live/archive fallback path, the collapsing of deep replies, or latency implications of choosing a source, all of which affect how the call behaves.

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?

A single short sentence with zero filler, front-loaded with the verb and the key scope detail. Nothing in it is redundant or padded.

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?

With five parameters, a non-trivial source-fallback behavior, and no output schema, the definition is thinner than the tool warrants. The parameters are fully self-documented, but an agent gets no help distinguishing this from the several comment-related siblings or understanding that the live path may fail and fall back to archive.

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 description coverage is 100%, with enums and defaults fully documented for source, comment_sort, comment_depth and comment_limit, so the schema does the heavy lifting and baseline 3 applies. The description contributes no additional parameter meaning beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Get a post') and adds a meaningful scope detail ('with its comment tree'), so the agent knows the response bundles comments. It does not differentiate from siblings such as get_comment_thread or get_comments_by_id, which is the only thing keeping it from a 5.

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?

There is no when-to-use guidance: nothing says whether to prefer this over get_comment_thread when only comments are needed, or over search_posts when the post id is unknown. The agent must infer the routing from the tool name alone.

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