bw_adso_get_xml
Get the raw ADSO XML needed for PUT updates. Use outputPath to write the full XML to disk, avoiding large inline responses and enabling reuse in later save/activate operations.
Instructions
Get the raw ADSO XML used for PUT updates. ALWAYS prefer outputPath — payloads are 15–80 KB. With outputPath, the full XML is written to disk (reuse as xmlPath in bw_adso_save_and_activate) and the MCP response is only a summary envelope. Without outputPath, format='summary' (default) returns a small overview; format='xml' returns the raw XML inline. Step 1 of read-modify-write.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| format | No | Only affects inline responses (no outputPath). summary (default) = overview; xml = raw XML. | |
| outputPath | No | If provided, the full result is written to this path (under the workdir) and the tool returns only a small summary envelope { ok, outputPath, bytes, summary }. Objects/arrays are written as JSON; ONLY the bw_*_get_xml family writes the raw XML string as plain text (that file is directly reusable as xmlPath in a later save call). Other *_get tools (e.g. bw_dtp_get, bw_trfn_get) write the PARSED XML-to-JSON tree, not raw XML — use the matching bw_*_get_xml tool when you need the raw XML string. Use outputPath for large responses (XML, table data, logs, dataflow graphs). When set, tools skip inline pagination/projection so the file contains the complete payload. | |
| forceCacheUpdate | No |