OpenApps

Use this when the user asks what changed in a store: chart moves, featuring, launches, delistings, metric moves or MCP changes, newest first with counts per type. Do not use for a chart's full current order; use charts_get.

Use this when the user asks which apps are new in a store since a time, by launch date or else the day each went live. Do not use for rank or toolset changes; use changes_list.

Use this when you need stores, app counts, countries, freshness, charts or metrics. Pass store for chart names. guide returns a playbook's steps: weekly_brief (a store's week), competitor_watch (compare apps), audit_my_server (an MCP server's tools). Do not use for rankings; use charts_get.

Use this when you need a chart now or at a past time, with movement and 1-based positions. Do not use for a listing across charts; use listings_profile.

Use this when the user asks which apps lead a store by a published number. claude: installs, popularity_score, trending_score, gh_stars; cursor: dir_installs, dir_stars. Do not use for chart positions; use charts_get.

Use this when the user asks which apps are popular in a store over the last month: OpenApps Rank, a 28-day aggregate of its popularity charts, with tier and momentum. Do not use for one day's chart order (charts_get) or published counts (leaderboards_get).

Use this when you need an app's ref from its name, its publisher, a brand it works with or what it does ("create jira ticket"); one row per app, best match first. Do not use for popularity or rankings; use charts_get.

Use this when you need when and where apps were featured, per app or home shelf, over at most 30 days. Do not use for current shelf order; use charts_get.

Use this when you need a listing profile, or up to 5 (Pro): its app, country availability, ranks, metrics and MCP tools. Stale or refused countries read unknown. Do not use for discovery; use listings_search.

Use this when you need a tracked app or server's stored MCP tools or changes. at selects a past snapshot; diff_from compares versions. Do not use for arbitrary URLs; only tracked servers.

Use this when you need store sizes, weekly launches, app kinds or MCP ecosystem statistics. Do not use for app profiles or rankings.

Use this when ChatGPT deep research needs listings, apps, tags (query tag:<id>), charts or tracked MCP URLs. Returns typed ids for fetch. Do not use for rankings or events; use charts_get or changes_list.

Use this when ChatGPT deep research needs a document for an id returned by search: listing, app, tag, chart or MCP toolset. Do not use for ids outside search results.

Use this when OpenApps' tools or data fail the user: an error, data the user says is wrong (such as an app bound to the wrong listing), a missing capability, or something confusing. Ask the user before sending a report they did not ask for. It is stored privately with the caller's account and client; no reply comes in this conversation. Summarize; never include secrets or personal data. Do not use for other servers or the client app; it does not finish the user's task.