create_scheduled_job
Schedule automated execution of SingleStore notebooks for tasks like ETL workflows, data aggregation, reporting, and maintenance. Supports one-time or recurring runs with optional snapshot backups.
Instructions
Create an automated job to execute a SingleStore notebook on a schedule.
Parameters:
- notebook_path: Complete path to the notebook
- mode: 'Once' for single execution or 'Recurring' for repeated runs
- create_snapshot: Enable notebook backup before execution (default: True)
Returns Job info with:
- jobID: UUID of created job
- status: Current state (SUCCESS, RUNNING, etc.)
- createdAt: Creation timestamp
- startedAt: Execution start time
- schedule: Configured schedule details
- error: Any execution errors
Common Use Cases:
1. Automated Data Processing:
- ETL workflows
- Data aggregation
- Database maintenance
2. Scheduled Reporting:
- Performance metrics
- Business analytics
- Usage statistics
3. Maintenance Tasks:
- Health checks
- Backup operations
- Clean-up routines
Related Operations:
- get_job_details: Monitor job
- list_job_executions: View job execution history
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| create_snapshot | Yes | ||
| ctx | No | ||
| mode | Yes | ||
| notebook_path | Yes |
Input Schema (JSON Schema)
{
"$defs": {
"Context": {
"description": "Context object providing access to MCP capabilities.\n\nThis provides a cleaner interface to MCP's RequestContext functionality.\nIt gets injected into tool and resource functions that request it via type hints.\n\nTo use context in a tool function, add a parameter with the Context type annotation:\n\n```python\n@server.tool()\ndef my_tool(x: int, ctx: Context) -> str:\n # Log messages to the client\n ctx.info(f\"Processing {x}\")\n ctx.debug(\"Debug info\")\n ctx.warning(\"Warning message\")\n ctx.error(\"Error message\")\n\n # Report progress\n ctx.report_progress(50, 100)\n\n # Access resources\n data = ctx.read_resource(\"resource://data\")\n\n # Get request info\n request_id = ctx.request_id\n client_id = ctx.client_id\n\n return str(x)\n```\n\nThe context parameter name can be anything as long as it's annotated with Context.\nThe context is optional - tools that don't need it can omit the parameter.",
"properties": {},
"title": "Context",
"type": "object"
}
},
"properties": {
"create_snapshot": {
"title": "create_snapshot",
"type": "string"
},
"ctx": {
"anyOf": [
{
"$ref": "#/$defs/Context"
},
{
"type": "null"
}
],
"default": null
},
"mode": {
"title": "mode",
"type": "string"
},
"notebook_path": {
"title": "notebook_path",
"type": "string"
}
},
"required": [
"notebook_path",
"mode",
"create_snapshot"
],
"title": "create_scheduled_jobArguments",
"type": "object"
}