Start Article Writer Pipeline
start_writer_pipelineEnqueue a writer-pipeline job for an existing WriterSession and get a jobId immediately, then poll status until done, failed, or aborted.
Instructions
Not available with an API key during the Article Writer's private beta: the server answers every API-key call to this tool with 404. Once the writer is public: enqueue a writer-pipeline job for an existing WriterSession. Returns immediately with a jobId; the orchestrator-worker claims it within ~5 seconds. Default section is step_7_5 — the auto-chain that replaces the three buttons in Step 7.5. Use get_writer_pipeline_status to poll until status is 'done', 'failed', or 'aborted'. Writer steps are billed in Science AI Journal credits.
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": {
"sessionId": "<sessionId>"
},
"name": "start_writer_pipeline"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | If true, abort any existing queued/running job for this (sessionId, section) and enqueue fresh. | |
| section | No | Which section to run. Default 'step_7_5' (the code-search → adapt → verify → simulate chain). | |
| language | No | Simulation language override (python | r | matlab | ...). | |
| sessionId | Yes | WriterSession id you already own. Create one via the web UI at /writer first; the MCP server does not own the session-creation flow today. |