Create a job
job_createCreate a job: named standing work in a workspace (founder-posts, inbox-triage), with a one-line purpose, a description its agents read, the agents who do it (each with an optional role; internal members' agents, a guest's is refused), and optionally its task definitions: each names the task types it covers, how to create one, and its steps with their role, cadence, instructions and approval. A job grants nothing: approvals stay per task. Jobs are internal (a guest never sees one). Your own jobs come first in workspace_load's jobs; name a job with job on task_create, task_update, task_report, task_propose (a new proposal) and task_start (by tags, with your step). A name already used in the workspace, an archived job's included, refuses JOB_NAME_TAKEN.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workspaceId": "<workspaceId>",
"name": "<name>"
},
"name": "job_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| why | No | Required for workspace items: one sentence on what the person is trying to accomplish, in their terms, not a description of this edit. Every workspace write takes one; sessions and summaries record themselves from it. At most 300 characters. | |
| name | Yes | The job's name, unique in the workspace (founder-posts, inbox-triage): lowercase letters, digits, - and _, starting with a letter or a digit, at most 64 characters. | |
| agents | No | The agents who do the job, at most 20, each once: { agent, role? }. A job grants nothing: approvals stay per task. | |
| purpose | No | One line on what the job is for, at most 280 characters ("The founder's notes become posts on X and LinkedIn"): shown under its name wherever jobs are listed, so a reader can tell which job does what. Empty is none. | |
| definitions | No | The job's task definitions, at most 5, in order: each says what a task of the job is (its types), how to create one (instructions) and the steps it goes through: { name, types, instructions?, steps }. The job's purpose, description and definitions take at most 30000 bytes as JSON. | |
| description | No | What the job is and how it is done, in markdown, at most 8000 characters: the standing brief its agents read. The job's purpose, description and definitions share 30000 bytes as JSON. | |
| workspaceId | Yes | The workspace (its id or its slug). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job | Yes |