Skip to main content
Glama
Sign In

FastAF

by co.fastaf
OverviewDiscussionsAdmin

Read Reddit Feed

read_reddit
Read-onlyIdempotent

Reads a public Reddit subreddit or thread through its public RSS feed and returns markdown (titles, dates, links, post text), capped at 12,000 characters. Author usernames and links to user profiles are removed, and the feed can hold fewer posts or comments than the website. It does not read user pages, and is not for other sites (use scrape_url). Required: url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired public reddit.com subreddit or thread URL, e.g. https://www.reddit.com/r/python/ or https://www.reddit.com/r/python/comments/abc123/; no default. Reads the public RSS feed only; user pages are refused. No option surcharge; 1 credits per successful request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Required public reddit.com subreddit or thread URL, e.g. https://www.reddit.com/r/python/; no default. Reads the public RSS feed only. No option surcharge; 1 credits per successful request."New value: +"Required public reddit.com subreddit or thread URL, e.g. https://www.reddit.com/r/python/ or https://www.reddit.com/r/python/comments/abc123/; no default. Reads the public RSS feed only; user pages are refused. No option surcharge; 1 credits per successful request."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavioral context beyond the annotations: output is markdown capped at 12,000 characters, author usernames and profile links are removed, and the RSS feed may contain fewer posts or comments than the website. These details are useful and do not contradict the readOnly, idempotent, non-destructive annotations.

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 front-loaded with the core behavior and then adds important caveats efficiently. 'Required: url' is somewhat redundant with the schema, but overall it is tight and well structured.

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?

For a single-parameter read tool with rich annotations and a fully described schema, the description covers output format, size cap, privacy redaction, feed limitations, and sibling routing. Nothing essential is missing.

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 coverage is 100%, and the schema already describes the required url parameter in detail. The description only repeats 'Required: url' without adding syntax or format meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: reading a public Reddit subreddit or thread via RSS, returning markdown. It clearly distinguishes itself from scrape_url for other sites, so an agent can select it without opening the schema.

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?

Explicitly says it does not read user pages and is not for other sites, naming scrape_url as the alternative. This gives clear when-to-use and when-not-to-use guidance.

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

All FastAF toolsInspect
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