Most questions you ask your AI assistant about AppFollow data start with a source: "our app," "our Android version," "the competitor set." To answer them correctly, the assistant needs to know exactly which sources you track and where. If you ask for a full map of your account first, you and the assistant get a shared reference point, and every later request resolves to the right source, platform, and country. In this article, you'll learn what this request returns, how to ask for it, and how to use the results in follow-up prompts.
Overview
When you ask your AI assistant for everything you're tracking, it reads your AppFollow account and returns:
- Every workspace in your account, with the number of sources in each
- For every source in those workspaces: the platform, store ID, country, current version, and publisher
This is a read-only request. Nothing in your account changes.
Why start here
The same source is often tracked more than once, for example on both the App Store and Google Play, or in several countries. Workspaces also tend to mix your own sources with competitors. When you say "our app," the assistant has to guess which one you mean unless it can see the full picture.
The map removes that guesswork. The store ID is the most reliable identifier to use, because source titles can change and similar sources can share almost identical names. It's also a light request, so it's a good way to open any session.
How to ask
Once AppFollow MCP is connected to your AI assistant, you can ask in plain language. For example:
What apps and workspaces do we have?More things to ask
- "Which of our apps are tracked on one platform but not the other?"
- "Which workspace is [app] in?"
- "List every competitor we track, grouped by workspace."
💡 Haven't connected yet? See AppFollow MCP and AI Toolkit for setup steps for each supported client.
Reading the results
| Field | What it means |
|---|---|
| Workspace | A group of sources in your AppFollow account |
| Source count | How many sources are tracked in that workspace |
| Platform | Where the app is published, such as the App Store or Google Play |
| Store ID | The store's own identifier: a number for App Store apps, a package name (like com.example.app) for Google Play apps |
| Country | The country the source is tracked in |
| Version | The latest version shown on the platform listing |
| Publisher | The developer name as it appears in the platform |
Using the map in follow-up requests
Keep the results in the same conversation and refer back to them. For example:
- Name the source by platform and country: "Our Google Play app in the US"
- Name a workspace to mean a whole group: "Compare ratings across the sources in my Competitors workspace"
- Ask the assistant to confirm which source it's using before it runs a longer analysis
F.A.Q.
Why does a Google Play app show "Varies with device" as its version?
Some Google Play apps ship different builds for different devices, so the store doesn't report a single version number. AppFollow shows what the store reports.
My assistant calls them "collections." Is that the same as workspaces?
Yes. "Collection" is the technical name for a workspace in AppFollow's API and MCP tools. They refer to the same thing.
A source I expected to see is missing. Why?
Only sources tracked in your AppFollow workspaces appear. You can add it in AppFollow, or ask your assistant to add it to a workspace for you. The assistant shows you what it's about to add and waits for your confirmation before anything changes.