Get All Projects
Get all projects that have geo presence tracking enabled. ALWAYS call this
first — every other tool needs a project_id, and this is the only place to get one.
Example: “List my projects to get project_id values for other endpoints.”
Only returns projects where a geo presence site has been configured. Projects without tracking setup are excluded.
Filters: optional query (substring on name/url). Pagination: limit (1-100, default 50) + offset; projects are sorted by creation date (newest first).
Response: data array (each item has id, name, url, created_at, type, markets — uppercase ISO country codes such as ["GB", "US"]) plus total (matches before paging), limit, offset. If total > items returned, page with offset — or narrow with query.
What project_id is and how to use it (read carefully):
- The
idfield of a project IS itsproject_id. It is a UUID like699aacd8-f75d-41b9-9fa8-7dde1bd82d02— NOT thenameorurl. - Steps: (1) find the project whose
name/urlmatches the user’s request, (2) take that project’sidvalue verbatim, (3) pass it as theproject_idargument on EVERY later tool call this conversation (reports, prompts, citations, sentiment, writes). - Resolve it ONCE and REUSE the same
id— do not re-list projects or change it unless the user switches projects. - You already have the id from this response: NEVER stop to ask the user for
the project id, and never treat a project’s
nameorurlas the id. - If exactly one project is returned, use its
iddirectly without asking.
TIP: when you only need one project’s id (e.g. the user named a brand or
domain), pass the query argument (that brand/domain) — it returns just the
matching project(s), so the list stays short and the id is always visible.
Body
Request parameters for retrieving all projects. All optional.