MCP documentation | MCP docs for agents
ark_add_manual_dispatch_location
ark.add_manual_dispatch_location
Add a manual dispatch location history entry for a visible ARK load, optionally sending the configured location-update notification in the same workflow.
- Availability
- Expanded preview
- Scopes
loads:write- ARK permissions
one of: canEditLoadone of: 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 for the dispatch location history entry.
format: uuid
dispatchIdstringrequiredDispatch ID that should receive the manual location history entry.
format: uuid
citystringrequiredCity for the manually reported dispatch location.
min length: 1; max length: 200
statestringrequiredState or province for the manually reported dispatch location.
min length: 1; max length: 6
countrystringone of: USA, CAN, MEX; default: "USA"
latitudenumber | nullmin: -90; max: 90
longitudenumber | nullmin: -180; max: 180
timezoneIdstring | nullIANA timezone ID for the manual location timestamp, when known.
max length: 100
locationDateTimestringISO timestamp for the manually reported location. Defaults to now.
format: date-time
sendNotificationbooleanWhen true, also sends the configured tracking location-update notification after saving the location.
default: false
Result
The tool returns the canonical ark.add_manual_dispatch_location 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.