model_transfer
ManagementcatalogTransfer Model
Not in the default tool list
This tool lives in the tool catalog. Discover it with scenario_tools_search (or enumerate everything with scenario_tools_list) and run it via scenario_tool_execute_write. To list every tool directly, connect with ?toolsets=full.
Transfer a model to a different project.
Args:
- model_id: required
- target_project_id: required — destination project ID
- team_id, project_id: required for OAuth callers
Returns: a job tracking the transfer operation.
Example: "Transfer this model to another project" -> model_id="model_xxx", target_project_id="project_yyy"
open-world
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| model_id | string | ✓ | Model ID. |
| target_project_id | string | ✓ | Destination project ID. |
| team_id | string | — | Team ID. Required if user belongs to multiple teams. |
| project_id | string | — | Project ID to scope the operation to. |
| response_format | enum(json | markdown) | json | Output format: 'json' for structured data, 'markdown' for human-readable text. |
Example Request
JSON
{
"model_id": "model_custom_abc",
"target_project_id": "proj_other456",
"team_id": "team_abc123",
"project_id": "proj_xyz789"
}Example Response
JSON
{
"job": {
"jobId": "job_transfer_001",
"status": "processing"
}
}Common Use Cases
- Transfer a trained model to another project for reuse across teams