MCP documentation | MCP docs for agents
ark_resolve_tracking_driver_conflict
ark.resolve_tracking_driver_conflict
Switch an active dispatch to the app-linked duplicate-phone driver and start internal ARK Tracking in one workflow.
- Availability
- Expanded preview
- Scopes
loads:dispatch- ARK permissions
canAssignLoads- Team visibility
- Required and enforced
- Approval policy
ask_before_send- ARK approval request
- Required before execution
- Idempotency
- Required for external execution
- Read-only
- No
- Destructive
- No
- External side effect
- Yes
- Rate limit
- OAuth MCP credential and organization budgets
Input
loadIdstringrequiredVisible ARK load ID.
format: uuid
dispatchIdstringrequiredVisible active dispatch whose driver should be switched.
format: uuid
targetDriverIdstringrequiredApp-linked driver ID suggested by the tracking conflict response.
format: uuid
emailCopiesTostring | nullmax length: 1000
notesstring | nullmax length: 5000
Result
The tool returns the canonical ark.resolve_tracking_driver_conflict operation result in structuredContent and mirrors the same JSON as text. Errors set isError: true and return a stable error code, message, and optional details.