# What Parse tracks for the brand

> parse_tracking: workspace reads tool on Parse's MCP server.

HTML: https://parse.gl/docs/mcp/tools/parse_tracking · Site index: https://parse.gl/llms.txt

Use when the user asks what is being tracked or wants to change it. Returns the brand's plan, markets, rivals, Custom topics (the `topics` field: each with its id, its name, the questions Parse asks it as, its source: "Added by you", "Only for" and the brand's name when Parse drafted it for this brand alone, or the market it belongs to) and the user's own notification switches. Read-only. On Pro, parse_add_topic, parse_remove_topic, parse_correct_rival and parse_set_notification change one.

## Who may call it

| Name | Access | Plan | Effect |
| --- | --- | --- | --- |
| `parse_tracking` | Sign-in with read access. Reading never changes or marks anything. | Free | Reads only |

## Input

| Argument | Type | Required | Notes |
| --- | --- | --- | --- |
| `brandSlug` | string | no | The brand's slug or its name. Omit it to use the workspace's own brand. |

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "brandSlug": {
      "description": "The brand's slug or its name. Omit it to use the workspace's own brand.",
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    }
  },
  "additionalProperties": false
}
```

## Example call

POST to `https://mcp.parse.gl/mcp` with `Content-Type: application/json` and `Accept: application/json, text/event-stream`, and the bearer token from Parse sign-in:

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "parse_tracking",
    "arguments": {}
  }
}
```

## Limits

Signed-in calls: 30 a minute per workspace, 2 at once, on any plan; 15 a minute for a workspace on Free. All limits are on [Plans and limits](https://parse.gl/docs/limits).