jobhunt.app/mcp

Review your activity history

See recorded changes with their dates and context.

Updated

Step by step

  1. Ask what changed

    Ask your connected agent to summarize recent recorded activity or changes on a particular saved application. Your agent reads each event in plain words, such as Resume section edited, with the record it is about.

  2. Check the history pages

    The activity feed has pages. Continue reading them until the requested event is found or the available history ends.

  3. Read attribution carefully

    Use only the actor and source details shown for an event. Missing attribution stays unknown; a client label does not prove which person or agent acted.

What happens next

You can review the activity recorded in JobHunt and where its available history ends.

Troubleshooting

The activity feed combines application history with a bounded window of recent account events. It is not a complete audit export, so an older event missing from the feed is not proof that it never happened.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READlist workspace activity

Read a page of the same owned work-history timeline as the browser. Follow has_more. The browser timeline combines application history with the latest 500 account events; it is not a complete audit export.

GET /api/v1/journey/list_workspace_activity_v2

DECLARED PERMISSIONS

  • read:activity
  • read:applications
View input, output and access requirements →