list_projects

list_projects MCP tool: list every project accessible to your Mentionable API key, with brand info, scan mode and selected LLMs. Cursor pagination, name filter, sort options.

Updated 2026-04-26

list_projects

list_projects returns every project the current Mentionable API key can see. It is the entry point of the MCP: most other tools take a projectId, so the agent calls list_projects first to resolve a name into an ID. The response carries brand data, target country, scan mode and the LLMs selected for tracking.

When to use

Call list_projects whenever the agent does not yet know which projectId to operate on. It is also the right tool when the user asks broad questions like "what do I track?", "list my brands", "which of my projects runs daily scans?". Combine it with a filters.nameContains to disambiguate when a workspace contains many projects with similar names.

Input

Field Type Default Description
cursor string Pagination cursor from a previous response.
limit integer 20 1 to 100.
filters.nameContains string Case-insensitive substring match on project name.
sortBy enum recent recent, oldest, alphabetical.

Response

A data array of project objects plus the standard pageInfo. Each project includes brand metadata, scan settings and the LLMs being tracked.

{
  "data": [
    {
      "id": "clx0000aaa",
      "name": "Acme Corp",
      "url": "https://acme.com",
      "brandName": "Acme",
      "brandAliases": ["Acme Inc", "Acme Corp"],
      "contentLanguage": "en",
      "contentTargetCountry": "US",
      "scanMode": "daily",
      "selectedLlms": ["CHATGPT", "PERPLEXITY", "GEMINI"],
      "createdAt": "2026-02-10T14:23:01.000Z",
      "updatedAt": "2026-04-25T08:00:00.000Z"
    }
  ],
  "pageInfo": { "hasMore": false, "nextCursor": null, "totalCount": 1 }
}

Tips and patterns

  • Always call list_projects first. Caching the resolved projectId in your agent state avoids paying for the lookup on every turn.
  • Use filters.nameContains for fuzzy resolution when the user mentions a brand by its short name.
  • selectedLlms tells you which engines the project actually tracks. Skip per-LLM filters for engines that are not in this array.
  • Read scanMode (daily or thrice_weekly) before reasoning about freshness of lastUpdated timestamps in downstream tools.

Related tools