> ## 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.

# List the work record

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

Read the workspace's shared work record: every pitch, listing, reply, published page, fix, note, and to-do with its status, target, owner, due date, latest note, and what changed after (outcomes show correlation, not proof of causation). Filter by brand, status, kinds, target, contact, topic, owner, goal, due, or since; pass item for one item's full trail, or view: "to\_file" / "contacts". Free.

## Who may call it, and what it costs

| Name | Access | Effect |
| - | - | - |
| `list_work` | A workspace key, or a sign-in with read access. | Reads only |

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

## Arguments

**brand** `string`

brd\_ id

**status** `list of one of planned, drafted, sent, no_reply, replied, won, declined, published, fixed, live, shipped, noted, done, suggested, open, reported, ended`

open (not ended), reported (an agent said won or live, monitoring has not agreed), ended, suggested (the tasks Parse suggests), or any status up to 17

**taken** `boolean`

with suggested: only the tasks another assistant holds

**kinds** `list of one of pitch, listing_request, reply, page_written, page_edit, correction, site_fix, note, pitched, pitch_sent, listed, declined, published, fixed`

item kinds; the older log\_work names (pitched, published, listed, declined, fixed) read as their kinds up to 15

**target** `string`

a page (URL or pg\_ id), a site (domain or site:), a contact (ct\_ id or email) or a top\_ id: items aimed at it

**page** `string`

the same as target, as older calls pass it

**contact** `string`

ct\_ id or email: items to or about that contact

**topic** `string`

top\_ id, or words of the gap

**owner** `string`

**goal** `string`

gol\_ id: the work filed under it

**due** `one of overdue, today, week or date`

open items due by then: overdue, today, week (the next 7 days) or a date

**since** `date`

YYYY-MM-DD: items changed on or after it

**item** `string`

itm\_ id: that item with its full trail and notes

**view** `one of items, to_file, contacts`

items (default); to\_file: notes Parse could not anchor; contacts: the workspace's contacts

**limit** `integer`

default 25; the token cap wins min 1, max 200

**cursor** `string`

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": {
    "brand": {
      "description": "brd_ id",
      "type": "string",
      "minLength": 3,
      "maxLength": 220
    },
    "status": {
      "description": "open (not ended), reported (an agent said won or live, monitoring has not agreed), ended, suggested (the tasks Parse suggests), or any status",
      "maxItems": 17,
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "planned",
          "drafted",
          "sent",
          "no_reply",
          "replied",
          "won",
          "declined",
          "published",
          "fixed",
          "live",
          "shipped",
          "noted",
          "done",
          "suggested",
          "open",
          "reported",
          "ended"
        ]
      }
    },
    "taken": {
      "description": "with suggested: only the tasks another assistant holds",
      "type": "boolean"
    },
    "kinds": {
      "description": "item kinds; the older log_work names (pitched, published, listed, declined, fixed) read as their kinds",
      "maxItems": 15,
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "pitch",
          "listing_request",
          "reply",
          "page_written",
          "page_edit",
          "correction",
          "site_fix",
          "note",
          "pitched",
          "pitch_sent",
          "listed",
          "declined",
          "published",
          "fixed"
        ]
      }
    },
    "target": {
      "description": "a page (URL or pg_ id), a site (domain or site:), a contact (ct_ id or email) or a top_ id: items aimed at it",
      "type": "string",
      "minLength": 3,
      "maxLength": 2000
    },
    "page": {
      "description": "the same as target, as older calls pass it",
      "type": "string",
      "minLength": 3,
      "maxLength": 2000
    },
    "contact": {
      "description": "ct_ id or email: items to or about that contact",
      "type": "string",
      "maxLength": 500
    },
    "topic": {
      "description": "top_ id, or words of the gap",
      "type": "string",
      "maxLength": 200
    },
    "owner": {
      "type": "string",
      "maxLength": 200
    },
    "goal": {
      "description": "gol_ id: the work filed under it",
      "type": "string",
      "maxLength": 60
    },
    "due": {
      "description": "open items due by then: overdue, today, week (the next 7 days) or a date",
      "anyOf": [
        {
          "type": "string",
          "enum": [
            "overdue",
            "today",
            "week"
          ]
        },
        {
          "type": "string",
          "format": "date"
        }
      ]
    },
    "since": {
      "description": "YYYY-MM-DD: items changed on or after it",
      "type": "string",
      "format": "date"
    },
    "item": {
      "description": "itm_ id: that item with its full trail and notes",
      "type": "string",
      "maxLength": 60
    },
    "view": {
      "description": "items (default); to_file: notes Parse could not anchor; contacts: the workspace's contacts",
      "type": "string",
      "enum": [
        "items",
        "to_file",
        "contacts"
      ]
    },
    "limit": {
      "description": "default 25; the token cap wins",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    },
    "cursor": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T[\\d:.]+Z\\|[0-9a-f-]{36}$"
    }
  },
  "additionalProperties": false
}
```

## Example call

The open work, with what falls due in the next 7 days. Over REST:

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

curl -s -X POST https://agent.parse.gl/v1/tools/list_work \
  -H 'content-type: application/json' \
  -H "Authorization: Bearer $PARSE_API_KEY" \
  -d '{"status":["open"],"due":"week"}'
```

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

```json theme={null}
{
  "method": "tools/call",
  "params": {
    "name": "list_work",
    "arguments": {
      "status": [
        "open"
      ],
      "due": "week"
    }
  }
}
```

More calls:

* Everything done on a page, by every brand of the workspace, with what happened after: `{"target":"https://example.com/best-tools"}`
* One item's trail and notes: `{"item":"itm_…"}`
* Notes Parse kept to file, each with the one thing it needs: `{"view":"to_file"}`

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.