Connect a client
Deploy a project
Deploy the configured source, or a completed source upload. The response acknowledges queued work and includes deploymentId: the build is done when getDeployment for that ID reports success or failed, which usually takes a few minutes. The operation handle only tracks the request.
Queued work: send an idempotencyKey and reuse the same value when retrying this exact call.
Arguments
| Name | Type | Required | Limits |
|---|---|---|---|
sourceUploadId | string | No | At least 1 character(s) |
projectId | string | Yes | At least 1 character(s) |
idempotencyKey | string | Yes | At least 1 character(s) |
Full input schema
{
"type": "object",
"properties": {
"sourceUploadId": {
"type": "string",
"minLength": 1
},
"projectId": {
"type": "string",
"minLength": 1
},
"idempotencyKey": {
"type": "string",
"minLength": 1,
"maxLength": 200,
"description": "Unique request key. Reuse this exact value when retrying the same operation."
}
},
"required": [
"projectId",
"idempotencyKey"
],
"additionalProperties": false
}Example call
The params of a tools/call request. Replace the placeholder values with your own IDs.
{
"name": "deployProject",
"arguments": {
"projectId": "REPLACE_WITH_PROJECT_ID",
"idempotencyKey": "REPLACE_WITH_IDEMPOTENCY_KEY"
}
} Result
The same data as the API operation, wrapped as {"untrusted_data": true, "source": "deployProject", "note": "...", "data": ...} so the model treats project content as data, not instructions.