Choose toolsets
Add?toolsets= to the URL, or send the X-Runtm-Toolsets header.
Toolsets:
core (always on), agents, sessions, context, guardrails, triggers, files (opt-in), lifecycle (opt-in). A misspelled toolset is an error that lists the valid names.
One tool per operation
?mode=tools (or X-Runtm-Mode: tools) replaces the curated tools with one tool per API operation, named runtm_<operation> (for example runtm_agents_create). Use it with MCP gateways that apply policy per tool name. Combine it with ?toolsets= to narrow the list.
Core (always on)
search and fetch use the names and shapes ChatGPT connectors expect.
Agents
Sessions
Context
Attached is not built. After attaching or changing a skill, MCP server, guardrail or context, run
runtm_build_template.Guardrails
Triggers
WhatsApp, SMS, Teams, voice and webhook triggers aren’t available over MCP yet. Use the dashboard.
Files (opt-in)
Lifecycle (opt-in)
Conventions
- Updates change only what you pass. To unset a field, list it in
clear. Anullargument is ignored, because some clients sendnullfor every field they leave out. - Credential steps return a link. Operations that take a key, token or password return
handoff_urlandnext_stepfor the person to finish in the dashboard. - Partial results don’t fail the call. Tools that combine several reads put what failed under
errorsorunavailable. - Long work returns a handle. Launch, build and deploy return at once. Follow up with
runtm_get_session_eventsorruntm_get_template. - Hints show safety. Read tools are marked read-only;
runtm_exec_command,runtm_write_fileand deletes are marked destructive.
Prompt and resource
- Prompt
build_agent(inputjob): builds an agent for a job by following Build an agent step by step. - Resource
runtm://skills/runtm: the same skill the Agent CLI installs.