Search Google Play App Listings

Search the stored US Google Play app catalog using words in app names and descriptions. Narrow the list with one app category, one rating condition, and one sort choice; up to 10 results are returned.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use google-app-listings-search-live through the existing Toolmu connection. Accept ordinary search words for app names and descriptions, one category, one rating or other supported filter condition, and one sorting preference. Do not ask the user to provide field names, operators, JSON, codes, or internal values. The Tool searches a stored US Google Play catalog only; it has no location, language, paging, or live-store option. Resolve the category against the current official Google App Listings category list and use exactly one supported category. Map the user’s plain-language filter to one condition supported by the official available-filters list. This Tool accepts one filter condition; its current numeric input contract permits 4.5, so do not send another numeric threshold. If a requested category or filter cannot be mapped exactly, explain that in ordinary words and ask the user to choose a supported option. Map one plain-language sort preference to a supported field and direction; the documented install-count sort is item.installs_count,asc. Ask for clarification if the requested order is unclear. Check current Tool availability and price and stay within the user’s existing execution authorization and budget. Submit the complete request with title, description, one category, one filter, one sort rule, and limit 10. Keep each search phrase within 200 characters for supplier compatibility. The result may match words from either field; the supplier does not document whether title and description are combined with AND or OR, so do not promise that every listing matches both or that phrase matching is exact. Show app names and Google Play links, with available ratings, install figures, review counts, and listing prices; do not show package IDs unless asked. Keep source-record dates separate from app release/update dates and preserve missing or null values instead of converting them to zero. Describe entries as candidates from the stored US catalog, not a live or complete inventory.

Task:
Find Google Play apps with [photo editor] in the name and [remove background] in the description. Use available U.S. listings, keep apps rated [4.5 stars or higher], sort by fewer reported installs first, and show up to 10 app names and links.

Paste into your connected AI's conversation.

Connection guide

Up to 0.320001 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

DataForSEO

Search Google Play App Listings

You receive

Receive matching app entries with available package IDs, names and store links. Records can also include ratings, review counts, prices with currencies, reported install figures and developer details. Your Agent can organize those values into a shortlist for inspecting the app listings.

Start with your task

Find Google Play apps with [photo editor] in the name and [remove background] in the description. Use available U.S. listings, keep apps rated [4.5 stars or higher], sort by fewer reported installs first, and show up to 10 app names and links.

What to know

Use nonempty title and description text of no more than 200 characters each. Results come from the stored US catalog, may contain fewer than 10 entries and can have missing details. A query does not establish a fresh store crawl. Source-record update dates and app release or update dates describe different events.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Listing search criteria`request`	`object`	Required	Required complete object with title, description, categories, order_by, filters and limit. These six properties must all be supplied. Required fields `title, description, categories, order_by, filters, limit`
Result cap`request.limit`	`integer`	Required	Required integer fixed at 10. This caps returned app entries; it does not guarantee 10 matches. Fixed value `10`
Title search text`request.title`	`string`	Required	Required nonempty string. Native length is 1–256 characters; use 1–200 characters for supplier compatibility. Supply this even when description text is also provided. Minimum length `1` Maximum length `256`
Additional filter`request.filters`	`array`	Required	Required array containing exactly one filter condition. Build one complete [field, operator, value] tuple with supplier-supported fields and operators. Minimum items `1` Maximum items `1`
Filter condition`request.filters[]`	`array`	—	Each condition is an array. The native structure permits 1–3 members, but a usable supplier condition needs all three: field, operator and value. Example: ["item.rating.value", ">", 4.5]. Minimum items `1` Maximum items `3`
Filter member`request.filters[][]`	`string \| number`	—	A string must contain 1–256 characters; the only permitted numeric member is 4.5. This numeric constraint does not require every search to filter by rating. Use a compatible complete condition.
Sorting rules`request.order_by`	`array`	Required	Required array with exactly one supported sorting rule. It orders the returned catalog records and is not an app chart ranking. Minimum items `1` Maximum items `1`
Sorting rule`request.order_by[]`	`string`	—	Required array item, a 1–256 character string containing a supported field, comma and asc or desc. Example: item.installs_count,asc. Minimum length `1` Maximum length `256`
App categories`request.categories`	`array`	Required	Required array containing exactly one supplier-supported Google Play category identifier. Minimum items `1` Maximum items `1`
Category identifier`request.categories[]`	`string`	—	Required array item, a nonempty 1–256 character string. Tools is an illustrative category value. Minimum length `1` Maximum length `256`
Description search text`request.description`	`string`	Required	Required nonempty string. Native length is 1–256 characters; use 1–200 characters for supplier compatibility. Supply both description and title text without assuming a Boolean matching rule. Minimum length `1` Maximum length `256`

View raw JSON

{
  "type": "object",
  "required": [
    "request"
  ],
  "properties": {
    "request": {
      "type": "object",
      "required": [
        "title",
        "description",
        "categories",
        "order_by",
        "filters",
        "limit"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "const": 10
        },
        "title": {
          "type": "string",
          "maxLength": 256,
          "minLength": 1
        },
        "filters": {
          "type": "array",
          "items": {
            "type": "array",
            "items": {
              "anyOf": [
                {
                  "type": "string",
                  "maxLength": 256,
                  "minLength": 1
                },
                {
                  "type": "number",
                  "const": 4.5
                }
              ]
            },
            "maxItems": 3,
            "minItems": 1
          },
          "maxItems": 1,
          "minItems": 1
        },
        "order_by": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 256,
            "minLength": 1
          },
          "maxItems": 1,
          "minItems": 1
        },
        "categories": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 256,
            "minLength": 1
          },
          "maxItems": 1,
          "minItems": 1
        },
        "description": {
          "type": "string",
          "maxLength": 256,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

For dates, distinguish the supplier’s record update from the app’s first release and last app update. A recent date for one event does not establish recency for the others.

The DataForSEO App Listings Search documentation explains the stored listing data and supported query fields.

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

Both text inputs are required. The supplier describes searches within the respective listing fields but does not specify an AND/OR combination, case handling or exact-phrase matching rule. Supply the words you want to search and inspect the actual returned listings.

Search Google Play App Listings

Search Google Play App Listings

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Choose search words

Choose a category and narrow the list

Review the app listings

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Choose search words

Choose a category and narrow the list

Review the app listings

Questions about this tool.

How do the title and description search words combine?

Does sorting by installs show the most popular apps?

Are review counts and rating votes the same?

Does a free flag mean there are no app purchases?

Why can the database total differ from the returned entries?