Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_post

Retrieve Reddit post details by URL without comments to inspect post content and metadata.

Instructions

reddit: Post. GET /v1/reddit/post. Get information from a Reddit post without comments Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "reddit_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesReddit post URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose billing behavior that the schema cannot: 1 credit on success, free for errors, blocked, timed-out, invalid, and cached requests. It says nothing about authentication requirements, rate limits, pagination, or what the returned payload looks like, so significant behavioral gaps remain.

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

Conciseness3/5

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

Purpose is front-loaded and findable, but the trailing pricing section spans three sentences of boilerplate, including the hedged 'charged only where that operation's published cost says so', which adds length without adding decision-relevant clarity.

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?

For a one-parameter read tool this covers what it does and what it costs, which is the core. Because there is no output schema and no annotations, the description should describe at least roughly what the post data contains (title, body, score, media) and whether it is a single object; that 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?

There is a single required parameter whose schema coverage is 100% and which ships an example URL, so the baseline is already satisfied. The description adds nothing further about URL format variants (short links, old.reddit, non-www), so it neither helps nor hurts.

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?

States a specific verb and resource ('Get information from a Reddit post') and adds the scope qualifier 'without comments', which implicitly separates it from reddit_post_comments. The 'reddit: Post. GET /v1/reddit/post.' prefix is machinery rather than meaning, but the intent is unambiguous.

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

Usage Guidelines3/5

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

The 'without comments' clause hints that reddit_post_comments exists for the commented variant, and the credit/caching sentences imply when calls are cheap (repeat/cached requests). However, there is no explicit when-to-use or when-not-to-use statement naming an alternative.

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

Deploy Server

Other Tools