> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Assistants connect to Parse over MCP at [https://agent.parse.gl/mcp](https://agent.parse.gl/mcp) (Streamable HTTP). With no sign-in it answers from Parse's public view (the numbers parse.gl's public pages show, up to 5 rows a list), starting with `check_brand`. Signed in with Parse, or sent a workspace key (`parse_mcp_…`), it works in the person's workspace, starting with `get_brief`. Scripts call the same tools over REST at `https://agent.parse.gl/v1/tools/<tool>`.
>
> ```bash
> npx parse-gl init
> ```
>
> To install just the skills: `npx skills add Parsegl/skills`.
> Every tool is also a POST to https://agent.parse.gl/v1/tools/<tool>; its OpenAPI description is https://agent.parse.gl/openapi.json.

# Get the brief, or the event log

> get_brief: a workspace tool on Parse for agents (agent.parse.gl). Arguments, price, and a call over REST and MCP.

Open a workspace's latest visibility changes, new citations, open work items, and due follow-ups. Call once at the start of any session about the brand's site, content, SEO, or marketing. Returns brands, standingInstructions, brandContext, goals, open/due work, job results, moves, and account/low-credit alerts. Reading marks the brief read unless peek: true. Use brand to scope, moves: true for weekly movers, chains: true for workflow patterns, or view: "events" for the full paged event log. Free.

## Who may call it, and what it costs

| Name | Access | Effect |
| - | - | - |
| `get_brief` | A workspace key, or a sign-in with read access. | Marks the brief read |

**Price.** Free. Every reply says what the call cost in `meta.costCredits`. The prices are on [Spending, tracking and stopping](/docs/credits.md).

## Arguments

**view** `one of brief, events`

brief (default): what passed the bar, ranked; events: every event

**since** `"last" or date or time`

"last" (default: since the last brief) or an ISO date or time; with view: "events", a day (UTC), in place of the last 7 days

**until** `date`

events only: only events on or before this day (UTC)

**sections** `list of one of changes, findings, pages, actions, rivals, jobs, account, nearby`

default all up to 8

**chains** `boolean`

add the common jobs, each as its chain of calls (always added while the workspace has no brand)

**moves** `boolean`

add every brand of the workspace (its own and those it watches), each in its own markets, this week against the week before, largest move first, one read for all

**brand** `string`

the brd\_ id of the brand this job is for, in a workspace that serves several (an agency's clients): the brief is about it, nobody is asked which brand is theirs, and nothing is claimed or billed

**peek** `boolean`

read the brief without marking it read, so the next call (this key's or another's) still starts where the last read did

**kinds** `list of string`

events only: only these kinds: mention\_move, rival\_move, finding, fact\_contradicted, page\_first\_cited, page\_dropped, page\_changed, proof\_step\_blocked, own\_page\_changed, action\_outcome, new\_answer\_batch, work\_item, work\_question, brief\_delivered, job\_finished, tracking\_paused, budget\_paused, auto\_topup, auto\_topup\_failed, auto\_topup\_skipped, credits\_expired, request\_decided, setting\_changed up to 20

**limit** `integer`

events only: default 25 min 1, max 200

**cursor** `string`

events only: the page.cursor (an event id) to continue after

Every argument the tool takes, as `GET /v1/tools` serves it, every shared object written out; `https://agent.parse.gl/openapi.json` serves the same schema with the filter and the window named once under `components` and pointed to by `$ref`. MCP `tools/list` leaves out the arguments few calls send, and says the filter and the window once, under `search_answers`; `resolve_ids {"kinds": ["argument"]}` lists what it left out, and a call with any of them runs:

```json theme={null}
{
  "type": "object",
  "properties": {
    "view": {
      "description": "brief (default): what passed the bar, ranked; events: every event",
      "type": "string",
      "enum": [
        "brief",
        "events"
      ]
    },
    "since": {
      "description": "\"last\" (default: since the last brief) or an ISO date or time; with view: \"events\", a day (UTC), in place of the last 7 days",
      "anyOf": [
        {
          "type": "string",
          "const": "last"
        },
        {
          "type": "string",
          "format": "date-time",
          "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
        },
        {
          "type": "string",
          "format": "date"
        }
      ]
    },
    "until": {
      "description": "events only: only events on or before this day (UTC)",
      "type": "string",
      "format": "date"
    },
    "sections": {
      "description": "default all",
      "maxItems": 8,
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "changes",
          "findings",
          "pages",
          "actions",
          "rivals",
          "jobs",
          "account",
          "nearby"
        ]
      }
    },
    "chains": {
      "description": "add the common jobs, each as its chain of calls (always added while the workspace has no brand)",
      "type": "boolean"
    },
    "moves": {
      "description": "add every brand of the workspace (its own and those it watches), each in its own markets, this week against the week before, largest move first, one read for all",
      "type": "boolean"
    },
    "brand": {
      "description": "the brd_ id of the brand this job is for, in a workspace that serves several (an agency's clients): the brief is about it, nobody is asked which brand is theirs, and nothing is claimed or billed",
      "type": "string",
      "minLength": 3,
      "maxLength": 220
    },
    "peek": {
      "description": "read the brief without marking it read, so the next call (this key's or another's) still starts where the last read did",
      "type": "boolean"
    },
    "kinds": {
      "description": "events only: only these kinds: mention_move, rival_move, finding, fact_contradicted, page_first_cited, page_dropped, page_changed, proof_step_blocked, own_page_changed, action_outcome, new_answer_batch, work_item, work_question, brief_delivered, job_finished, tracking_paused, budget_paused, auto_topup, auto_topup_failed, auto_topup_skipped, credits_expired, request_decided, setting_changed",
      "maxItems": 20,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[a-z_]{2,40}$"
      }
    },
    "limit": {
      "description": "events only: default 25",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    },
    "cursor": {
      "description": "events only: the page.cursor (an event id) to continue after",
      "type": "string",
      "pattern": "^\\d{1,18}$"
    }
  },
  "additionalProperties": false
}
```

## Example call

What changed for the workspace's brands since the last brief. Over REST:

```bash theme={null}
export PARSE_API_KEY="<your-key>"

curl -s -X POST https://agent.parse.gl/v1/tools/get_brief \
  -H 'content-type: application/json' \
  -H "Authorization: Bearer $PARSE_API_KEY" \
  -d '{}'
```

Over MCP, the assistant calls the tool by name with the same arguments:

```json theme={null}
{
  "method": "tools/call",
  "params": {
    "name": "get_brief",
    "arguments": {}
  }
}
```

More calls:

* Every brand's move this week against last, largest first: `{"moves":true}`
* The brief for one client's brand, in a workspace that serves several: `{"brand":"<brd_ id>"}`
* Read the brief without marking it read for this key: `{"peek":true}`
* Everything new in the workspace in the last 7 days, oldest first: `{"view":"events","limit":20}`
* Only one brand's events, between two days: `{"view":"events","brand":"<brd_ id>","since":"2026-11-01","until":"2026-11-12"}`

The reply has `data`, `context`, `next`, `page` and `meta`; follow `next` for the calls that come after. A refused call returns `{ code, message, fix }`: see the [error table](/docs/mcp-reference.md#errors).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.