freshcontext-mcp

extract_reddit

Read-only

Analyze Reddit community sentiment by fetching posts, scores, comment counts, and timestamps from subreddit or search URLs.

Instructions

Extract posts and community sentiment from Reddit via the public JSON API. Accepts a subreddit URL (https://www.reddit.com/r/MachineLearning/.json), a search URL, or a subreddit shorthand ('r/MachineLearning'). Returns titles, authors, scores, comment counts, and per-post timestamps.

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": "extract_reddit"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Subreddit URL, search URL, or 'r/<subreddit>' shorthand
`max_length`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.1Sep 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The readOnlyHint annotation is true, and the description does not contradict it. The description adds useful behavioral details about returning specific post fields and using the public JSON API, which goes beyond the annotation.

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 concise, using two sentences to convey the tool's purpose, input formats, and output fields. No extraneous information is included.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lists the return fields, which addresses the lack of an output schema. However, the ambiguity around 'max_length' leaves a minor gap in understanding the tool's full behavior, though overall it is adequate for a simple extraction tool.

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?

The schema covers only the 'url' parameter with a description; 'max_length' has no description in the schema or in the tool description. The description does not clarify the meaning or effect of 'max_length', leaving its semantics ambiguous. Since coverage is only 50%, the description fails to compensate.

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 the tool extracts posts and sentiment from Reddit, specifies accepted URL formats, and lists the returned fields. This is a specific verb and resource, and it is distinct from sibling tools that target other sources.

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

Usage Guidelines4/5

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

The description explicitly states the accepted inputs (subreddit URL, search URL, or shorthand), making it clear when to use this tool. It does not explicitly mention alternatives, but the context of sibling tools specialized in other sources makes the usage context implicit yet sufficiently clear.

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