Skip to main content
Glama

rowfeed/app-reviews-scraper

rowfeed--app-reviews-scraper
Destructive

This tool calls the Actor "rowfeed/app-reviews-scraper" and retrieves its output results. Actor description: Export Google Play and App Store reviews of any app: rating, title, text, date, app version, helpful votes and the developer's reply. Paste store links, package names or App Store ids, any country. Newest or most relevant first. About $0.10 per 1,000 reviews.

Input Schema

NameRequiredDescriptionDefault
appsNoOne app per line: a Google Play or App Store link, a package name (com.spotify.music) or an App Store id (324684580). Up to 500 per run. Example values: ["https://play.google.com/store/apps/details?id=com.spotify.music","https://apps.apple.com/us/app/spotify-music-and-podcasts/id324684580"]
sortByNoNewest first, or the store's most relevant / most helpful first. Example values: "newest"newest
countryNoStore country, e.g. "United States", "United Kingdom", "Germany". Reviews differ per country. Example values: "United States"United States
languageNoStore language, e.g. "English", "German". Example values: "English"English
waitSecsNoMax 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.
newerThanNoLeave out older reviews: a date (2026-10-01) or an age (7 days, 2 weeks, 3 months). Left-out reviews are not charged. With "Newest first", no further reviews are fetched once the cutoff is reached, which makes scheduled monitoring cheap.
maxReviewsNoHow many reviews to get per app, in the chosen order. Up to 10,000 on Google Play; the App Store gives at most 500 per app and country. Example values: 20

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "app_id": {
      +      "type": "string"
      +    },
      +    "app_rating": {
      +      "type": "number"
      +    },
      +    "app_ratings_total": {
      +      "type": "number"
      +    },
      +    "app_title": {
      +      "type": "string"
      +    },
      +    "app_url": {
      +      "type": "string"
      +    },
      +    "app_version": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "checked_at": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": "string"
      +    },
      +    "developer_replied_at": {
      +      "type": "null"
      +    },
      +    "developer_reply": {
      +      "type": "null"
      +    },
      +    "from_snapshot": {
      +      "type": "boolean"
      +    },
      +    "helpful_count": {
      +      "type": "null"
      +    },
      +    "position": {
      +      "type": "number"
      +    },
      +    "published_at": {
      +      "type": "string"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "rating": {
      +      "type": "number"
      +    },
      +    "review_id": {
      +      "type": "string"
      +    },
      +    "review_text": {
      +      "type": "string"
      +    },
      +    "sort": {
      +      "type": "string"
      +    },
      +    "store": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / apps / prefill
      Added value: +[
      +  "https://play.google.com/store/apps/details?id=com.spotify.music",
      +  "https://apps.apple.com/us/app/spotify-music-and-podcasts/id324684580"
      +]
    • addedInput schema / properties / country / prefill
      Added value: +"United States"
    • addedInput schema / properties / language / prefill
      Added value: +"English"
  3. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Live lookups need a paid Apify plan (any plan). The pre-filled example works on the free plan."
  4. Changed1 schema field changed
    • removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Removed value: -{
      -  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      -  "properties": {
      -    "app_id": {
      -      "type": "string"
      -    },
      -    "app_rating": {
      -      "type": "number"
      -    },
      -    "app_ratings_total": {
      -      "type": "number"
      -    },
      -    "app_title": {
      -      "type": "string"
      -    },
      -    "app_url": {
      -      "type": "string"
      -    },
      -    "app_version": {
      -      "type": [
      -        "null",
      -        "string"
      -      ]
      -    },
      -    "checked_at": {
      -      "type": "string"
      -    },
      -    "country": {
      -      "type": "string"
      -    },
      -    "developer_replied_at": {
      -      "type": "null"
      -    },
      -    "developer_reply": {
      -      "type": "null"
      -    },
      -    "from_snapshot": {
      -      "type": "boolean"
      -    },
      -    "helpful_count": {
      -      "type": "null"
      -    },
      -    "position": {
      -      "type": "number"
      -    },
      -    "published_at": {
      -      "type": "string"
      -    },
      -    "query": {
      -      "type": "string"
      -    },
      -    "rating": {
      -      "type": "number"
      -    },
      -    "review_id": {
      -      "type": "string"
      -    },
      -    "review_text": {
      -      "type": "string"
      -    },
      -    "sort": {
      -      "type": "string"
      -    },
      -    "store": {
      -      "type": "string"
      -    },
      -    "title": {
      -      "type": [
      -        "null",
      -        "string"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}
  5. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "app_id": {
      +      "type": "string"
      +    },
      +    "app_rating": {
      +      "type": "number"
      +    },
      +    "app_ratings_total": {
      +      "type": "number"
      +    },
      +    "app_title": {
      +      "type": "string"
      +    },
      +    "app_url": {
      +      "type": "string"
      +    },
      +    "app_version": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "checked_at": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": "string"
      +    },
      +    "developer_replied_at": {
      +      "type": "null"
      +    },
      +    "developer_reply": {
      +      "type": "null"
      +    },
      +    "from_snapshot": {
      +      "type": "boolean"
      +    },
      +    "helpful_count": {
      +      "type": "null"
      +    },
      +    "position": {
      +      "type": "number"
      +    },
      +    "published_at": {
      +      "type": "string"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "rating": {
      +      "type": "number"
      +    },
      +    "review_id": {
      +      "type": "string"
      +    },
      +    "review_text": {
      +      "type": "string"
      +    },
      +    "sort": {
      +      "type": "string"
      +    },
      +    "store": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  6. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare openWorldHint and destructiveHint, and the description adds genuinely useful context beyond them: cost (~$0.10 per 1,000 reviews), the paid-plan requirement for live lookups, and that filtered-out reviews are not charged. It does not explain why destructiveHint is set for what reads as a scrape, which is the one gap.

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?

Two sentences, front-loaded with the resource and followed by the field list and pricing. The opening 'calls the Actor ... and retrieves its output results' is boilerplate that could be trimmed, but nothing else is wasted.

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 no explanation, and the description covers cost, plan requirements and the waitSecs polling behavior. For a 7-parameter, zero-required scraper this is close to complete, missing only explicit sibling differentiation.

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% and the schema already documents apps, sortBy, country, language, waitSecs, newerThan and maxReviews in detail. The description adds only the cost implication of newerThan, so the baseline 3 applies.

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?

The description names a specific verb and resource: it exports Google Play and App Store reviews with the exact fields returned (rating, title, text, date, version, votes, developer reply). It is clearly distinguishable from metadata scrapers like google-play-scraper, though it never explicitly contrasts itself with those siblings.

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?

Usage is implied through 'Paste store links, package names or App Store ids, any country' and the sort options, which tells an agent how to invoke it. There is no explicit when-to-use/when-not guidance and no mention of the sibling app-store scrapers that might be alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.