Find Reddit leads and brand mentions. AI buyer labels and Slack or Notion delivery. $1.50/1k results
Scored across 5 tools
The four generic Apify tools target clearly distinct objects (run, dataset, key-value record) and actions. The Reddit scraper actor is the domain entry point; it could momentarily overlap with dataset/run retrieval, but the descriptions clarify the division of labor.
Most tools follow a consistent kebab-case verb_noun pattern: abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record. The actor tool harshmaur--reddit-scraper-pro breaks the pattern with a double hyphen and no verb, making the set read as mixed conventions.
Five tools is a reasonable size for a single-actor workflow plus supporting run/result retrieval helpers. Nothing feels bloated, though the surface is slightly thin for the broader lead-monitoring purpose implied by the server name.
The set covers actor run inspection, abortion, dataset result retrieval, and key-value record access, which is solid infrastructure. However, it lacks explicit start-run/listing operations and any tools for scheduling, monitoring, or alert management despite those being core to the server's stated purpose.
Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.
USAGE:
Use when you need to stop a run that is taking too long or misconfigured.
USAGE EXAMPLES:
user_input: Abort run y2h7sK3Wc
user_input: Gracefully abort run y2h7sK3Wc
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | The ID of the Actor run to abort. | |
| gracefully | No | If true, the Actor run will abort gracefully with a 30-second timeout. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the no-effect-on-terminal-states rule, which is exactly what makes the idempotent hint meaningful, plus the fact that updated run details come back. It omits auth/permission requirements and any rate-limit behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core action and the state constraint, and every prose sentence earns its place. The 'USAGE EXAMPLES' block of raw user_input lines is mostly decorative and pads the definition slightly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 spelled out, and the description still notes that updated run details are returned. For a two-parameter mutation with full annotation coverage, only auth requirements are unaddressed, which is a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both parameters and the 30-second graceful-abort timeout are already documented in the schema. The description only gestures at 'gracefully' via an example, adding no syntax or semantic meaning beyond the schema. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb (Abort) plus resource (Actor run) and a state qualifier ('currently starting or running'), which immediately distinguishes it from siblings like call-actor and get-actor-run. 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit when-to-use ('stop a run that is taking too long or misconfigured') and an explicit no-op condition (terminal statuses such as SUCCEEDED, FAILED, ABORTED, TIMED-OUT). It does not name an alternative tool or describe prerequisites, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get detailed information about a specific Actor run.
Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.
USAGE:
Use to check the status of a run started by any Actor-running tool.
Pass waitSecs > 0 to block until terminal (or until the cap elapses).
USAGE EXAMPLES:
user_input: Show details of run y2h7sK3Wc
user_input: Wait for run y2h7sK3Wc to finish
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | The ID of the Actor run. | |
| waitSecs | No | Maximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT). 0 returns immediately with the current status. Cap: 45. Default: 30. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, but the description adds real behavioral context beyond them: the summary vs. nextStep semantics, and that waitSecs blocks for up to 45s (default 30) before returning the current state. This is substantive added value, though it doesn't cover error/failure modes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose, then segmented into Returns/USAGE/EXAMPLES blocks. Every line carries information, though the two usage examples are somewhat redundant with the USAGE prose, adding minor length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present and 100% parameter coverage, the description need only orient the agent, which it does fully: purpose, when to use, wait semantics, and concrete invocation examples. Nothing needed to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description goes further by framing waitSecs as a blocking/wait mechanism with its cap and default, and by describing what runId's run produces. Slight above-baseline value over the schema text.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get detailed information about a specific Actor run') and enumerates the returned result fields (status, storages, stats, summary, nextStep). It does not explicitly distinguish itself from siblings like call-actor or abort-actor-run, so it falls just short of the 5 benchmark.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The USAGE block names the condition ('check the status of a run started by any Actor-running tool') and explains when to pass waitSecs > 0 to block until terminal. It gives clear context but stops short of explicit exclusions or naming the sibling to use for other run operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.
USAGE:
Use when you need to read data from a dataset (all items or only selected fields).
USAGE EXAMPLES:
user_input: Retrieve results from dataset abc123
user_input: Get only metadata.url and title from dataset username~my-dataset
| Name | Required | Description | Default |
|---|---|---|---|
| desc | No | If true, results are returned in reverse order (newest to oldest). | |
| omit | No | Comma-separated list of fields to exclude from results. | |
| clean | No | If true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true. | |
| limit | No | Maximum number of items to return. Default is 20. | |
| fields | No | Comma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. "metadata.url"); the server auto-flattens parent prefixes. | |
| offset | No | Number of items to skip at the start. Default is 0. | |
| flatten | No | Comma-separated list of fields to flatten (e.g. flatten="metadata" turns {"metadata":{"url":"x"}} into {"metadata.url":"x"}). Normally derived automatically from dot-notation in `fields`; specify only as a diagnostic override. | |
| datasetId | Yes | Dataset ID or username~dataset-name. |
| Name | Required | Description |
|---|---|---|
| items | Yes | Dataset items |
| limit | Yes | Limit used for pagination |
| offset | Yes | Offset used for pagination |
| summary | Yes | Summary of the result |
| nextStep | Yes | One follow-up action with tool name |
| datasetId | Yes | Dataset ID |
| itemCount | Yes | Number of items returned |
| totalItemCount | Yes | Total items in dataset |
| apifyConsoleUrl | No | Personalized Apify Console link to the dataset; present only for Console sessions |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With annotations already declaring readOnlyHint=true and idempotentHint=true, the description adds valuable behavioral context: returns rows themselves, default limit of 20, and clean=true behavior. It also clarifies the nature of the return value beyond the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Well-structured with clear USAGE and USAGE EXAMPLES sections. Some redundancy ('Get items (rows)...' and 'Returns the rows themselves...') but overall efficient and front-loaded with purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 8 parameters, an output schema, and rich annotations, the description adequately covers key behaviors, usage triggers, and examples. It doesn't explain every parameter but relies on the schema for that, which is appropriate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds extra meaning by explaining default limit (20) and the clean=true shortcut, which supplements the schema. It also provides examples for fields usage, though most parameter semantics are in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool gets items (rows) from a dataset and explicitly distinguishes it from metadata, counts, or schema. It names the exact resource (dataset items) and the action (get), and provides direct trigger phrases for when to use it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit use cases ('when the user provides a datasetId and asks to retrieve results...'), and clarifies what it is not for (metadata, counts, schema). However, it does not name alternative tools explicitly, only implies them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically.
USAGE:
Use when you need to retrieve a specific record (JSON, text, or binary) from a store.
USAGE EXAMPLES:
user_input: Get record INPUT from store abc123
user_input: Get record data.json from store username~my-store
| Name | Required | Description | Default |
|---|---|---|---|
| recordKey | Yes | Key of the record to retrieve. | |
| keyValueStoreId | Yes | Key-value store ID or username~store-name. |
| Name | Required | Description |
|---|---|---|
| key | Yes | Record key |
| value | Yes | The stored value (JSON, text, or binary) |
| summary | Yes | Summary of the result |
| contentType | No | MIME type of the stored value |
| keyValueStoreId | Yes | Key-value store ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds genuine context beyond that: the exact key name is required, and the response preserves the original Content-Encoding with most clients decompressing automatically. That encoding note is real operational value an agent would otherwise not know.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core action and scope, then a short behavioral note, then usage. The USAGE line slightly overlaps the first sentence, but the examples earn their space by showing realistic inputs. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present there is no need to describe return values, and the annotations carry the safety profile. For a two-parameter read tool, the description supplies everything else an agent needs: exactness of the key, allowed value types, and the encoding caveat.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description still adds a semantic constraint the schema omits — that the key must be an exact match — and the examples show the 'username~my-store' form of the store ID, gently reinforcing the ID format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb (get) + resource (value under a key in a key-value store) with an explicit scope boundary: 'a single record, not a listing of all keys.' None of the sibling tools overlap with this resource, and the anti-scope clause removes any ambiguity about whether it enumerates keys.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The USAGE line gives a clear triggering condition — retrieving a specific record (JSON, text, or binary) — and two concrete examples anchor it. It lacks explicit when-not-to-use guidance or named alternatives, but no similar sibling exists to route against.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
This tool calls the Actor "harshmaur/reddit-scraper-pro" and retrieves its output results. Actor description: Find leads and track brand mentions on Reddit. Monitor buying-intent phrases like "is there a tool", competitor names and keywords, flag real buyers with an AI label, and get new posts in Slack or Notion on a daily schedule. Social listening with no Reddit API key, from $1.50 per 1,000 results.
| Name | Required | Description | Default |
|---|---|---|---|
| hasPain | No | Adds `aiFlags.hasPain` (true/false) to every analyzed post and comment: true when the author describes a problem, a failed tool, or something not working. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| isOwner | No | Adds `aiFlags.isOwner` (true/false) to every analyzed post and comment: true when the author founded, owns, or operates a business (not a customer or employee). Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| mcpMode | No | perPost: send one message/record per scraped post. summary: send a single digest of the whole run. Example values: "perPost" | perPost |
| mcpTool | No | Force a specific tool name on the connector (e.g. send_message, create_page, append_row). Leave empty to auto-detect the connector's write/notify tool. | |
| isVendor | No | Adds `aiFlags.isVendor` (true/false) to every analyzed post and comment: true when the author is selling, promoting, or recruiting testers for their own product or service. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| mcpTarget | No | Where to write — the destination ID the tool needs: a Notion database/page ID, a Google Sheet ID, a Slack channel, or owner/repo. Leave blank for connectors that post to a default location. Advanced shapes go in Arguments JSON below. | |
| painPoint | No | Adds `aiFlags.painPoint` (text) to every analyzed post and comment: the problem or unmet need in under 15 words, or none. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| startUrls | No | Add one or more Reddit URLs to scrape directly. Supports post URLs, subreddit URLs, user profile URLs, and search page URLs. The Search Keywords options above (sort, time, community filter) do NOT apply to these URLs. | |
| wantsHelp | No | Adds `aiFlags.wantsHelp` (true/false) to every analyzed post and comment: true when the author is looking for a product, service, or person to solve their problem — the classic lead signal. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| aiAnalysis | No | Adds AI-judged fields to posts and comments: `sentimentLabel` (positive / negative / neutral / mixed / uncertain), `sentimentScore` (-1 to 1), `intent` (question, seeking_recommendation, complaint, praise, purchase_intent, comparison, announcement, self_promotion, discussion), `emotion` (joy, excitement, anger, frustration, sadness, disappointment, fear, surprise, neutral), `entities` (brands, products and companies mentioned), and — for keyword-search results — `relevanceScore` (0 to 1). [Description truncated] | |
| competitor | No | Adds `aiFlags.competitor` (text) to every analyzed post and comment: the competing product, brand, or tool mentioned, or none. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| mcpMessage | No | Template for each message. Use {{field}} placeholders from ANY post field — common ones: {{title}}, {{body}}, {{postUrl}}, {{authorName}}, {{score}}, {{upVotes}}, {{commentsCount}}, {{communityName}}, {{flair}}, {{createdAt}}. Nested/array fields work via dot or [index] paths: {{mediaAssets.0.url}}, {{galleryImages[0]}}, {{media.reddit_video.fallback_url}}. (Full field list in the README.) Missing fields render empty. Example values: "**{{title}}**\n{{postUrl}}" | **{{title}}** {{postUrl}} |
| searchSort | No | Controls how keyword search results are ranked. Only applies to Search Keywords, not Direct URLs. Example values: "new" | new |
| searchTime | No | Limit keyword search results to posts from a specific time window. Only applies to Search Keywords. Example values: "week" | all |
| includeNSFW | No | Include posts marked as Not Safe For Work in results. Applies to both Search Keywords and Direct URLs. | |
| mcpComments | No | When 'Scrape comments for each post' is on, choose how comments reach your app. Ignore: send posts only (comments still saved to the dataset). Bundle: attach each post's top comments inside its message. Separate: send each top comment as its own message/record. Example values: "ignore" | ignore |
| mcpMaxItems | No | Safety cap on how many posts are piped to the connector per run (perPost mode). Protects against flooding the destination. Example values: 50 | |
| postedAfter | No | Only keep posts created on or after this date (00:00 UTC), or within a relative period counted back from the run start, e.g. '1 day' for a daily schedule or '7 days' for a weekly one. When set, results are fetched newest-first (sort=new) and the search Time range is ignored. Reddit caps each listing at ~1,000 posts, so a window behind a very high-volume query may be only partly reachable. Applies to Search Keywords, subreddit URLs, the Full Subreddit Scrape, and user profiles. | |
| searchPosts | No | Include posts in keyword search results. Example values: true | |
| searchTerms | No | Enter one or more keywords to search Reddit (e.g. "recommend a CRM", "alternative to HubSpot", or your brand name). Keep each phrase short: Reddit search is literal, so a long sentence usually finds nothing. Each keyword runs as a separate search. Free Apify plans search the first 40 keywords per run (paid plans are unlimited) — extra keywords are skipped and noted in the run log. Quoted phrases return fewer posts, especially inside one community. [Description truncated] Example values: ["recommend a CRM","alternative to HubSpot","looking for a CRM"] | |
| customLabels | No | Define your own labels as `{"label_name": "plain-language instruction"}` and the AI evaluates each one on every analyzed post and comment, returning them under `customLabels` on each result. Example: `{"mentions_pricing": "true if the text complains about pricing or cost", "competitor": "name the competing product mentioned, or none"}`. Up to 5 labels; names must be short identifiers (letters, digits, underscore). The AI flag checkboxes above do not count against this cap. [Description truncated] Example values: {"wants_software":"true only if the author wants to find, buy or switch to a software product; false for job posts, hiring a person, news, and authors advertising their own product"} | |
| mcpArguments | No | Extra/override arguments merged into each tool call as JSON — e.g. {"channel": "#reddit"} for Slack. {{field}} placeholders work inside string values too, so you can nest live data into any shape the tool needs — e.g. Notion: {"properties": {"Title": {"title": [{"text": {"content": "{{title}}"}}]}, "Link": {"url": "{{postUrl}}"}}}. Use it to satisfy required fields or fully control the payload. | |
| mcpConnector | No | Pick an authorized MCP connector (Slack, Notion, GitHub, Airtable, Supabase, …) to receive the scraped posts. This is the recommended, secure path — your credentials stay in Apify and are never exposed to this actor (Apify's proxy injects them). Leave empty to scrape only. Create connectors under Settings → API & Integrations → MCP connectors, or inline here. | |
| mcpServerUrl | No | Advanced/testing only. Connect directly to a raw MCP server URL, bypassing the MCP Connector above. For real use prefer a connector — with a connector your credentials stay in Apify and are never seen by this actor. When set, this overrides the connector. | |
| postedBefore | No | Only keep posts created on or before this date (the end of that day, 23:59:59 UTC). A relative value such as '1 day' keeps only posts at least one day old. | |
| willingToPay | No | Adds `aiFlags.willingToPay` (true/false) to every analyzed post and comment: true when the author names a budget, asks for a quote, or says they would pay. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| maxPostsCount | No | Maximum posts saved for EACH search keyword and EACH Reddit URL: 5 keywords × 50 = up to 250 posts. Full Subreddit Scrape uses this as one total. Each saved post is a billed result. Reddit search returns up to about 2,000 posts for a busy keyword; use Full Subreddit Scrape for more. Max: 50000. Example values: 25 | |
| mentionsPrice | No | Adds `aiFlags.mentionsPrice` (true/false) to every analyzed post and comment: true when the text mentions a price, fee, retainer, subscription cost, or money spent. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| onlyWithFlair | No | When enabled, drop posts with no flair and keep only those that have a flair assigned. Applies to Search Keywords, subreddit URLs, the Full Subreddit Scrape, and user profiles. | |
| subredditUrls | No | Subreddits to scrape in full. Enter subreddit names or links — e.g. `AskReddit`, `r/AskReddit`, or `https://www.reddit.com/r/AskReddit/`. This collects far more posts per subreddit than a standard scrape. It uses more requests, so runs take longer and cost more. Comments are also collected when 'Scrape comments for each post' is enabled — increase Max posts to allow more results per subreddit. | |
| commentedAfter | No | Only keep comments created on or after this date (UTC), or within a relative period such as '1 day' for a daily schedule. Applies when comments are collected (comment search, or 'Scrape comments for each post'). | |
| featureRequest | No | Adds `aiFlags.featureRequest` (true/false) to every analyzed post and comment: true when the author asks for or describes a feature or product that does not exist yet. Billed as one `custom_label` event per result ($0.10 per 1,000). | |
| mcpServerToken | No | Bearer token for the dev MCP server URL above. Note: a token entered here IS visible to the actor at runtime — for production use an MCP Connector instead, so credentials never leave Apify. Ignored unless the URL is set. | |
| searchComments | No | Include comments in keyword search results. Each comment is a billed result (up to 'Max search comments' per keyword). Example values: true | |
| commentedBefore | No | Only keep comments created on or before this date (UTC). | |
| withinCommunity | No | Restrict keyword search to a single subreddit. This is a name, not a post limit. Accepts a bare name (developers), r/developers, or a full subreddit URL. Leave empty to search all of Reddit. Only applies to Search Keywords. | |
| maxCommentsCount | No | Maximum comments returned per search keyword (when 'Search for comments' is enabled). Does not affect per-post comment scraping. | |
| searchCommunities | No | Include communities (subreddits) in keyword search results. | |
| maxCommentsPerPost | No | Maximum comments to scrape per individual post (when 'Scrape comments for each post' is enabled). Each comment is a billed result: 50 posts × 200 comments can be 10,000 results. | |
| mcpCommentsPerPost | No | How many top comments (by score) to include per post when bundling or sending comments. Requires 'Scrape comments for each post'. Example values: 5 | |
| maxCommunitiesCount | No | Maximum communities returned from keyword search (when 'Search for communities' is enabled). Example values: 2 | |
| crawlCommentsPerPost | No | When enabled, comments will be collected for every post found from both Search Keywords and Direct URLs. This significantly increases run time and data output. Each comment is a billed result: 50 posts × 200 comments can be 10,000 results. Example values: true |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the mutating/open-world profile is covered. The description adds essentially nothing behavioral on top of that: it never mentions that the call starts a billable Actor run, that it is asynchronous, or that waitSecs caps the wait and nextStep polling may be required — all of which materially affect how an agent should call it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action, with no repetition or filler. The second sentence is an Actor marketing blurb whose density is acceptable but slightly sales-oriented rather than operational.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and schema coverage is complete, so return-value explanation is not required. However, for a tool with 43 parameters that kicks off a potentially long, billable, destructive-by-annotation Actor run, the description omits the run lifecycle (start, wait cap, poll via get-actor-run), which is the one thing the schema cannot convey. Adequate but with a real gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% across all 43 parameters, and each parameter carries a substantive description (billing notes, search semantics, comment modes). The main description contributes no parameter meaning of its own, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb+resource (calls the Actor 'harshmaur/reddit-scraper-pro' and retrieves its output) and the embedded Actor blurb specifies the domain (Reddit social listening/lead finding). It is distinguishable from the generic siblings (get-dataset-items, get-actor-run) by naming the exact Actor. It stops short of a 5 because it is boilerplate wrapper phrasing plus marketing copy rather than a crisp statement of what the agent gets back.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to invoke this tool versus the sibling tools (get-actor-run for polling, get-dataset-items for raw output, abort-actor-run). The marketing blurb describes the Actor's value, not the agent's routing decision. Nothing states prerequisites, cost, or the async/run-start nature of the call in the description itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
harshmaur--reddit-scraper-pro9 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / crosspostParentId / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / crosspostParentUrl / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / distinguished / typePrevious value: -[
- "null",
- "string"
-]New value: +"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / media / typeRemoved value: -"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / removedByCategory / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / secureMedia / typeRemoved value: -"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / videoUrl / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "number",
- "null"
-]New value: +[
+ "null",
+ "number"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "null",
- "number"
-]New value: +[
+ "number",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "number",
- "null"
-]New value: +[
+ "null",
+ "number"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "null",
- "number"
-]New value: +[
+ "number",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "number",
- "null"
-]New value: +[
+ "null",
+ "number"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "null",
- "number"
-]New value: +[
+ "number",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]harshmaur--reddit-scraper-pro9 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / crosspostParentId / typePrevious value: -[
- "null",
- "string"
-]New value: +"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / crosspostParentUrl / typePrevious value: -[
- "null",
- "string"
-]New value: +"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / distinguished / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / media / typeAdded value: +"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / removedByCategory / typePrevious value: -[
- "null",
- "string"
-]New value: +"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / secureMedia / typeAdded value: +"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / videoUrl / typePrevious value: -[
- "null",
- "string"
-]New value: +"null"harshmaur--reddit-scraper-pro9 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / crosspostParentId / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / crosspostParentUrl / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / distinguished / typePrevious value: -[
- "null",
- "string"
-]New value: +"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / media / typeRemoved value: -"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / removedByCategory / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / secureMedia / typeRemoved value: -"null"Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / videoUrl / typePrevious value: -"null"New value: +[
+ "null",
+ "string"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "number",
- "null"
-]New value: +[
+ "null",
+ "number"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "null",
- "number"
-]New value: +[
+ "number",
+ "null"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "null",
- "string"
-]New value: +[
+ "string",
+ "null"
+]harshmaur--reddit-scraper-pro4 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / authorFullname / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / bodyHtml / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / depth / typePrevious value: -[
- "number",
- "null"
-]New value: +[
+ "null",
+ "number"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / flair / typePrevious value: -[
- "string",
- "null"
-]New value: +[
+ "null",
+ "string"
+]Find leads in Reddit, HN, X, Bluesky and Facebook group mentions, scored by AI, from your agent
Find high-intent Reddit conversations and manage lead workflows from MCP-compatible AI agents.
Track what people say about your product on Reddit, X, Hacker News, GitHub and more
Reddit growth toolkit — opportunities, replies, cold DMs, brand mentions, SEO, autopilot.
Add one secure layer between your agents and this server.
