Docs
Why AI says this about the brand
parse_why: workspace reads tool on Parse's MCP server.
Use when the user asks why AI describes their brand a certain way, or why it recommends a rival. Returns Parse's standing insights (what is still true of the brand) and what changed in the last two weeks (Activity's change lines) as short claims. Next, on Pro: parse_evidence with a returned typed reference reads the answers behind it, and standing cards open with parse_evidence using the returned typed reference. Increase weeks for older claims.
Who may call it
| Name | Access | Plan | Effect |
|---|---|---|---|
parse_why | 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. |
offset | integer | no | min 0, max 10000, default 0 |
weeks | integer | no | min 2, max 13, default 2 |
{
"$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
},
"offset": {
"default": 0,
"type": "integer",
"minimum": 0,
"maximum": 10000
},
"weeks": {
"default": 2,
"type": "integer",
"minimum": 2,
"maximum": 13
}
},
"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:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "parse_why",
"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.