Google Play App Search, Lookup & Reviews Scraper: one-request API, MCP and n8n

Google Play apps, reviews, permissions, data safety labels, developer catalogs, and similar apps.

Server mode on Also answers single HTTP requests with the results in the response. Call it as an API.

Fastest route, one HTTP request (results in the response):

curl -H "Authorization: Bearer $APIFY_TOKEN" \
  "https://vcknmnj5f5o6x56ho.apify.actor/?mode=search&searchQuery=calculator&maxItems=3"

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper" --name google-play-app-search-lookup-and-reviews-scraper

Every file on this page is generated from the Actor's published schema: 58 of 58 checks pass (validated, not run)
  • MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
  • n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
  • code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
  • SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)
  • server snippets: 7 of 7 (Server host is a resolvable apify.actor name (DNS label of 63 characters or fewer); The Actor publishes an OpenAPI 3 schema for its server; Multi-line shell commands continue every line with a backslash; Every example parameter is declared in the server schema; The example stays inside the per-request caps; Slashes in values are encoded (the platform collapses // in request paths); Token comes from APIFY_TOKEN, none embedded)

What the checks cover

What a run costs

Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.

Results in one runStartResultsRun total
10$0.40$0.010$0.41
100$0.40$0.10$0.50
1,000$0.40$0.99$1.39

Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.

MCP config

One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:

Claude Code configterminal or .mcp.json

claude mcp add --transport http google-play-app-search-lookup-and-reviews-scraper "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper"

Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup

Tools your agent gets

Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).

  • fetch-actor-detailsreads the input schema
  • nimbryxo-studio--google-play-app-search-lookup-and-reviews--8819sends one request to the Actor's server

This Actor has a server interface, so its tool sends one HTTP request instead of starting a batch run. For batch runs add call-actor to the tools list: https://mcp.apify.com/?tools=fetch-actor-details,call-actor,nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper

Call it as an API: one request, one answer

Server mode is switched on for this Actor (single-tenant, checked 2026-11-12 through the Apify API). Instead of starting a run and reading a dataset, send the input as an HTTP request to https://vcknmnj5f5o6x56ho.apify.actor/ and the results come back in the response. The request starts a run in your own Apify account, billed at the Actor's normal price.

Send one lookup and get the results back in the response. It takes the same input as a normal run: query parameters with GET, or a JSON body with POST. At most 100 results and 240 seconds per request; start a normal run for bigger jobs. Requests run in your own Apify account at the Actor's normal price.

From the Actor's published server schema.

curl (GET)

Server tab on Apify
curl -H "Authorization: Bearer $APIFY_TOKEN" \
  "https://vcknmnj5f5o6x56ho.apify.actor/?mode=search&searchQuery=calculator&maxItems=3"

Parameters and per-request caps

ParameterTypeCap
mode requiredstring (7 options)none
searchQuerystringnone
appIdsarray10 values
packageNamesarray10 values
startUrlsarray10 values
developerIdstringnone
developerNamestringnone
countrystring (50 options)none
languagestring (30 options)none
maxItemsintegermax 50
maxReviewsPerAppintegermax 100
reviewSortstring (3 options)none
includeDetailsbooleannone
includePermissionsbooleannone
includeDataSafetybooleannone
proxyConfigurationstringnone

Response codes

200
The results as a JSON array (at most 100). They are also saved to the run's dataset and billed per result, like a normal run.
400
Invalid, missing or unknown input fields. Nothing ran.
422
The Actor could not complete this request (for example, nothing matches). No results were delivered.
500
Unexpected failure. Safe to retry.
504
The request used up its 240 s budget. The results found so far are in partialItems.

Example response

The first record of the example response in the Actor's own server schema, long values shortened. Nothing was run for this page.

[
  {
    "packageName": "com.sec.android.app.popupcalculator",
    "appId": "com.sec.android.app.popupcalculator",
    "id": "com.sec.android.app.popupcalculator",
    "name": "Samsung Calculator",
    "title": "Samsung Calculator",
    "url": "https://play.google.com/store/apps/details?id=com.sec.android.app.popupcalculator",
    "sourceUrl": "https://play.google.com/store/apps/details?id=com.sec.android.app.popupcalculator",
    "summary": "[Key features]\nPerform four fundamental operations and engineering calculations.\n\nTo start the engineering calculator, tap the engineering calculator icon.\n\n...",
    "developer": "Samsung Electronics Co.,  Ltd.",
    "developerUrl": "https://play.google.com/store/apps/developer?id=Samsung+Electronics+Co.%2C++Ltd.",
    "rating": 4.45,
    "score": 4.45,
    "scoreText": "4.5",
    "icon": "https://play-lh.googleusercontent.com/p8rUJZjn-oJQPhrNASuJEZu3njkIxXP6P_AdeSUrXl5BrrtZDBu_YUBxJp0_WgcsaQ5HnB5-j9Fa7whGc0vo6w",
    "price": 0,
    "currency": "USD",
    "free": true,
    "searchQuery": "calculator",
    "rank": 1,
    "isExactMatch": false,
    "recordType": "app",
    "language": "en",
    "country": "us",
    "scrapedAt": "2026-11-10T15:33:11.818504+00:00"
  }
]

Download the OpenAPI file Open the Actor on Apify

The OpenAPI file is the Actor's published schema with the server URL and bearer auth filled in, so tools that import OpenAPI (custom GPT actions, Postman, API client generators) can call it directly.

n8n workflow

A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.

Send the records to
  • Run by hand
  • Every day
  • Run Apify Actor

n8n workflowgoogle-play-app-search-lookup-and-reviews-scraper.n8n.json

Actor on Apify
{
  "name": "Google Play App Search, Lookup & Reviews Scraper to n8n only",
  "nodes": [
    {
      "id": "0f8dad36-b2dd-4579-a6c7-13a818de1aeb",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "3aee001e-f16d-4d4f-a23f-fa363103b483",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "80f7759a-3f90-48bc-a881-f341dc163a3b",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/nimbryxo-studio~google-play-app-search-lookup-and-reviews-scraper/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"mode\": \"search\",\n  \"searchQuery\": \"calculator\",\n  \"country\": \"us\",\n  \"language\": \"en\",\n  \"maxItems\": 3,\n  \"maxReviewsPerApp\": 100,\n  \"reviewSort\": \"newest\",\n  \"includeDetails\": false,\n  \"includePermissions\": false,\n  \"includeDataSafety\": false\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "04e2d9ee-d9c1-4d7f-a164-e28a8d918d53",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## Google Play App Search, Lookup & Reviews Scraper\n\nSource: [nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper](https://apify.com/nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.

All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.

Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).

Download the long-run workflow11 of 11 checks pass, not executed

Call it from code

Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records; for a single lookup the server request above is faster. The input is the example below.

curl

API docs on Apify
curl -X POST "https://api.apify.com/v2/actors/nimbryxo-studio~google-play-app-search-lookup-and-reviews-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","searchQuery":"calculator","country":"us","language":"en","maxItems":3,"maxReviewsPerApp":100,"reviewSort":"newest","includeDetails":false,"includePermissions":false,"includeDataSafety":false}'

Example input

These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.

Actor inputinput.json

{
  "mode": "search",
  "searchQuery": "calculator",
  "country": "us",
  "language": "en",
  "maxItems": 3,
  "maxReviewsPerApp": 100,
  "reviewSort": "newest",
  "includeDetails": false,
  "includePermissions": false,
  "includeDataSafety": false
}

FieldTypeWhat it does
mode required string (7 options) What to scrape.
searchQuery string Keyword to search for in mode=search, for example photo editor or calculator.
appIds array Package names or Google Play URLs. Used by details, reviews, similar, permissions, and dataSafety modes.
packageNames array Android package names such as com.whatsapp. Play URLs are also accepted.
startUrls array Full Google Play app URLs, for example https://play.google.com/store/apps/details?id=com.whatsapp.
country string (50 options) Storefront for search results, pricing, and availability. Reviews are selected by Language, not Country.
language string (30 options) Language for app pages and the review bucket. Google Play uses this language, not Country, to choose reviews.
maxItems integer Hard cap on dataset rows. Search returns at most 250 apps per query. For similar mode one seed app is one row.
maxReviewsPerApp integer Reviews to collect for each app. Google Play returns at most 4,500 reviews per page; the actor paginates up to this cap.
reviewSort string (3 options) Order used when fetching reviews.
includeDetails boolean Fetch the full app page for search and developer results, and include app metadata in permissions/dataSafety output. Adds one request per app.
includePermissions boolean Add the app's permission list to app records. Works in search, details, developer, and similar modes.
includeDataSafety boolean Add shared data, collected data, security practices, and the privacy policy URL to app records.

3 more optional fields on the Store input tab.

What your agent receives

Each run returns a list of records. The Actor publishes 87 fields, starting with id, packageName, appId, name.

FieldWhat it holdsFormat
idStable identifier. For app records this is the Android package name; for reviews it is the review ID.string
packageNamePackagetext
appIdApp IDtext
nameApptext
titleBackward-compatible alias of name.string
urlURLtext
sourceUrlURL the record was collected from.string
developerDevelopertext
developerIdGoogle Play developer ID.string
developerUrlDeveloper catalog URL.string
30 more fields
FieldWhat it holdsFormat
developerEmailDeveloper contact email.string
developerWebsiteDeveloper website.string
developerAddressDeveloper contact address.string
developerLegalNameLegal developer name.string
developerLegalEmailLegal developer email.string
developerLegalAddressLegal developer address.string
developerLegalPhoneLegal developer phone number.string
privacyPolicyPrivacy policy URL.string
ratingRatingnumber
scoreBackward-compatible alias of rating.number
scoreTextRating as displayed by Google Play.string
ratingCountRatingsnumber
ratingsBackward-compatible alias of ratingCount.integer
reviewCountTotal number of written reviews.integer
histogramRating distribution from 1 star to 5 stars.array
installsInstallstext
minInstallsLower bound of the install estimate.integer
maxInstallsUpper bound of the install estimate.integer
realInstallsGoogle Play install estimate.integer
pricePricenumber
currencyCurrencytext
priceTextLocalized price text.string
freeWhether the app is free.boolean
offersIAPWhether the app offers in-app purchases.boolean
IAPRangeDisplayed in-app purchase range.string
genreGenretext
genreIdPrimary genre ID.string
categoriesCategories as objects with name and id.array
versionLatest app version when Google Play publishes it.string
updatedUpdatedtext

47 more fields in the full output.

Agent skill

A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.

SKILL.mdgoogle-play-app-search-lookup-and-reviews-scraper/SKILL.md

---
name: google-play-app-search-lookup-and-reviews-scraper
description: "Google Play apps, reviews, permissions, data safety labels, developer catalogs, and similar apps. Runs the Apify Actor nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper. Use when the user needs Google Play data with fields such as id, packageName, appId, name, title, url and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper"
  store-url: "https://apify.com/nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper"
---

# Google Play App Search, Lookup & Reviews Scraper

Use this skill to fetch Google Play data with the Apify Actor `nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `search`, `details`, `reviews`, `developer`, `similar`, `permissions`, `dataSafety`, required | What to scrape. |
| `searchQuery` | string | Keyword to search for in mode=search, for example `photo editor` or `calculator`. |
| `appIds` | array | Package names or Google Play URLs. Used by details, reviews, similar, permissions, and dataSafety modes. |
| `packageNames` | array | Android package names such as `com.whatsapp`. Play URLs are also accepted. |
| `startUrls` | array | Full Google Play app URLs, for example `https://play.google.com/store/apps/details?id=com.whatsapp`. |
| `country` | string | Storefront for search results, pricing, and availability. Reviews are selected by Language, not Country. |
| `language` | string | Language for app pages and the review bucket. Google Play uses this language, not Country, to choose reviews. |
| `maxItems` | integer | Hard cap on dataset rows. Search returns at most 250 apps per query. For similar mode one seed app is one row. |
| `maxReviewsPerApp` | integer | Reviews to collect for each app. Google Play returns at most 4,500 reviews per page; the actor paginates up to this cap. |
| `reviewSort` | one of `newest`, `rating`, `helpfulness` | Order used when fetching reviews. |
| `includeDetails` | boolean | Fetch the full app page for search and developer results, and include app metadata in permissions/dataSafety output. Adds one request per app. |
| `includePermissions` | boolean | Add the app's permission list to app records. Works in search, details, developer, and similar modes. |
| `includeDataSafety` | boolean | Add shared data, collected data, security practices, and the privacy policy URL to app records. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "search",
  "searchQuery": "calculator",
  "country": "us",
  "language": "en",
  "maxItems": 3,
  "maxReviewsPerApp": 100,
  "reviewSort": "newest",
  "includeDetails": false,
  "includePermissions": false,
  "includeDataSafety": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~google-play-app-search-lookup-and-reviews-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~google-play-app-search-lookup-and-reviews-scraper/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `id`, `packageName`, `appId`, `name`, `title`, `url`, `sourceUrl`, `developer`, `developerId`, `developerUrl`, `developerEmail`, `developerWebsite`, `developerAddress`, `developerLegalName`, `developerLegalEmail`, `developerLegalAddress`, `developerLegalPhone`, `privacyPolicy`, `rating`, `score`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.

  • Claude Code: save it as ~/.claude/skills/google-play-app-search-lookup-and-reviews-scraper/SKILL.md, or .claude/skills/google-play-app-search-lookup-and-reviews-scraper/SKILL.md in a project.
  • Codex and other agents: ~/.agents/skills/google-play-app-search-lookup-and-reviews-scraper/SKILL.md, or .agents/skills/google-play-app-search-lookup-and-reviews-scraper/ in a project.
  • Or let the skills CLI place it for your agent: npx skills add https://recipeforagents.com --skill google-play-app-search-lookup-and-reviews-scraper
  • Set APIFY_TOKEN in the agent's environment.

Recipes with this Actor

  • Google Play reviews to Google Sheets

    Log the newest Google Play reviews for an Android app in a Google Sheet. Columns follow the review records the Actor…

    Google PlayGoogle Sheets

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Questions

How do I connect Google Play App Search, Lookup & Reviews Scraper to Claude?

In Claude Code run: claude mcp add --transport http google-play-app-search-lookup-and-reviews-scraper "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/google-play-app-search-lookup-and-reviews-scraper and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.

What input does Google Play App Search, Lookup & Reviews Scraper need?

The published input schema requires mode. The example on this page uses the Actor's own Store prefill.

What does Google Play App Search, Lookup & Reviews Scraper cost to run?

The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.

Can I call Google Play App Search, Lookup & Reviews Scraper as a plain HTTP API?

Yes. Server mode is on for this Actor, so a GET or POST to https://vcknmnj5f5o6x56ho.apify.actor/ with an Authorization: Bearer header and the input as query parameters or a JSON body returns the results in the response. Each request runs in your own Apify account at the Actor's price.

Which tools does the MCP config give my agent?

2 tools: fetch-actor-details, nimbryxo-studio--google-play-app-search-lookup-and-reviews--8819. Apify's MCP server listed them for this exact URL on 2026-11-11.