Skip to main content
Keep the work record, so the next session knows what happened. It records what happens in the person’s work: what they sent, what came back, what was published or fixed, what was decided (including not to act, or to wait), each as an item with a status. Research is a note on the item or target it concerns. Examples: a pitch sent { “kind”: “pitch”, “target”: “<page URL>”, “status”: “sent”, “at”: “<the day it went; omit for today>” }; the editor replied { “item”: “itm_…”, “status”: “replied”, “text”: “<what they said>” }; a page published { “kind”: “page_written”, “target”: “<its URL>”, “status”: “published”, “at”: “<the day it went up: yesterday is that date>” }; decided not to pitch a page { “kind”: “pitch”, “target”: “<URL>”, “status”: “declined”, “text”: “<why>” }; a message that bounced or has not gone out yet { “kind”: “reply”, “target”: “<URL>”, “status”: “planned”, “text”: “bounced: <why>” }; one note about several pages: one item per page in items; wait and follow up { “move”: “plan”, “item”: “itm_…”, “due”: “next thursday”, “text”: “<why>” }; research with no action { “text”: “<what you found>”, “target”: “<page or site>” }. Pass brand when the workspace has several. Parse replies with the item it understood; the same brand, kind and target later updates it (item names one; a plan is a new item unless item names one), and the next get_brief starts from it. A reply with notFiledYet or notRead carries the call that completes the write. items for several. The declined_offer kind records an offer the person declined, by its offer id. Free.

Who may call it, and what it costs

Price. Free. Every reply says what the call cost in meta.costCredits. The prices are on Spending, tracking and stopping.

Arguments

one of plan, log, update
plan: work to do (planned); log: something done (default); update: change an item (with item)
string
what happened or is planned, in your words; pasted email text is fine (up to 4,000 characters)
string
a short title; default the note’s first sentence, cut to 80 characters
string
pitch, listing_request, reply, page_written, page_edit, site_fix or note; plan (or todo, task) is a to-do, as move plan; the older published, pitched, reply, listed, declined, fixed still work
string
outreach: planned, drafted, sent, no_reply, replied, declined; content: planned, drafted, published; site_fix: planned, shipped; note: noted, planned, done (open, todo and pending mean planned; bounced, failed, not sent mean planned, the word kept). An explicit status wins over the kind’s default. won and live are recorded as reported until Parse’s monitoring agrees
string
brd_ id, or the brand’s name or domain; default the workspace’s brand when it has exactly one
string
what it is aimed at: a page URL or pg_ id, a site (domain or site:), a contact’s email or ct_ id, a top_ id
string
the page, as older calls pass it: a pg_ id or URL
string or object
who it went to: “Jane Doe, Editor, [email protected]”, an address, a ct_ id, or { name, role, email, site }
string
why: a top_ id, or the gap in words
string
why: a qst_ id
string
when to follow up: a date, today, tomorrow, a weekday, next week, in 3 days
string
who does the work, to hand it to someone: a person’s name; default this key’s label on a new item. Who wrote each change is kept on its event
where the work lives: a doc, a PR, a thread
string
itm_ id: the item to update
string
nt_ id: file a note kept to file, with what it lacked
boolean or string
true: let status move back or one end change to another, recorded as a correction
string
when it happened: a date, or yesterday or a weekday; default today. A page that went up yesterday is at yesterday
string
the playbook followed, as get_playbook named it (kind@version)
string
the same as text
one of first_questions, track_weekly, keep_running, top_up
with kind declined_offer: the offer’s id
list of object
several notes in one call (up to 50), each with the fields above; the call’s own fields apply to each as defaults up to 50
The schema as tools/list 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:

Example call

A note as you have it: Parse files it as an item on the page, with the contact, and replies with what it understood. Over REST:
Over MCP, the assistant calls the tool by name with the same arguments:
More calls:
  • Plan several pieces of work at once: to-dos are items in planned: {"move":"plan","brand":"<brd_ id>","items":[{"kind":"pitch","target":"https://example.com/best-tools","due":"2026-11-20"},{"kind":"page_written","topic":"pricing comparison","owner":"Dana"}]}
  • Update an item: a second session or another agent writing the same brand, kind and target updates it too: {"item":"itm_…","status":"replied","text":"The editor wants a quote from the CEO"}
  • The older call, which works as before: a pitch sent to a page: {"kind":"pitched","page":"https://example.com/best-tools","brand":"<brd_ id>","note":"Emailed the editor"}
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.