artifact_put
Register file, text, JSON, Markdown, or HTML artifacts in a resolved workspace from a path or inline UTF-8 content. Store metadata and classify artifacts for Nexus-managed projects.
Instructions
Register a file/text/json/markdown/html artifact in the resolved workspace. Docs: okto-nexus://reference/tool-docs/artifacts.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_root": "<project_root>",
"artifact_type": "<artifact_type>"
},
"name": "artifact_put"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Human-friendly name/label for the artifact (optional). | |
| path | No | Filesystem path to import into Nexus-managed artifact storage (must stay within the workspace root). Provide this OR content - at least one REQUIRED. | |
| content | No | UTF-8 content stored outside the database (bounded by max_inline_bytes; json must be well-formed). Provide this OR path - at least one REQUIRED. | |
| metadata | No | Free-form JSON object stored with the artifact (optional). | |
| project_root | Yes | Absolute path to the project (defines the workspace scope). | |
| artifact_type | Yes | Artifact classification - one of: file, text, json, markdown, html. REQUIRED. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||