Skip to main content
Glama
tacps126

webdata-tools-mcp

by tacps126
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Reddit posts and comments

search_reddit
Read-onlyIdempotent

Search Reddit posts and comments by keyword, subreddit, or user to monitor brands and topics. Returns titles, text, authors, scores, links, and dates as structured JSON.

Instructions

Reddit posts (and optionally comments) by keyword, subreddit or user: title, text, author, subreddit, score, links and dates. Good for brand and topic monitoring. Runs the Apify Actor tacps126/reddit-monitor on your Apify account (about $0.001 per post or comment; spend per call is capped at $0.5).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoResult order.new
timeNoTime window for keyword searches.week
keywordsNoSearch all of Reddit; "exact phrase" works.
max_itemsNoMaximum results to return (default 50, max 500). Cost scales with this.
subredditsNoSubreddit names, e.g. ["webscraping"].
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
include_commentsNoAlso return comments of the matched posts (more results, higher cost).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / include_comments / description
      Added value: +"Also return comments of the matched posts (more results, higher cost)."
    • addedInput schema / properties / sort / description
      Added value: +"Result order."
    • addedInput schema / properties / time / description
      Added value: +"Time window for keyword searches."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "Number of records the Actor returned.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "items": {
+      "description": "The records. Long text fields are shortened to 600 characters.",
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "shown": {
+      "description": "Number of records included in `items` (can be lower than count when the result is long).",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "tool": {
+      "description": "Name of the tool that produced the result.",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "True when records were left out to keep the result short; ask for fewer items.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "tool",
+    "count",
+    "shown",
+    "truncated",
+    "items"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: it runs the third-party Actor tacps126/reddit-monitor on the caller's Apify account, costs roughly $0.001 per item, and is capped at $0.5 per call. It does not cover auth prerequisites or failure behavior, so not a 5.

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?

Three compact sentences that lead with scope and filters before moving to cost and execution model. The field list (title, text, author, subreddit, score, links, dates) is somewhat redundant given an output schema exists, but the overall density is high.

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?

With an output schema present, return values need not be explained, and the description correctly spends its words on cost, execution environment, and filter scope instead. The main gap is the absence of any note on authentication or what happens when the spend cap is hit mid-call.

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%, so every parameter (sort, time, keywords, subreddits, max_items, include_comments, extra_input) is already documented in the schema. The description restates the filter dimensions but adds no format or syntax detail beyond what the schema provides, so the baseline of 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 (Reddit posts and optionally comments) with the filter dimensions (keyword, subreddit, user) and the fields returned. It is clearly distinguishable from siblings like search_google_news or get_trustpilot_reviews, which target entirely different sources.

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?

"Good for brand and topic monitoring" implies a use case but gives no when-not guidance, no prerequisites, and does not route to any alternative sibling. The agent can infer intent but gets no decision boundary.

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