whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_bundle_import

Destructive

Imports a project bundle into a selected hosted WhoDB project and returns a confirmation token so users can preview and approve changes before applying.

Instructions

Import a project bundle into the selected hosted project.

Use whodb_platform_bundle_import_plan first when possible. Default mode returns a confirmation token; do not call whodb_platform_confirm until the user approves the import preview. Supports prefix, rename_conflicts, and overwrite_conflicts. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

Name	Required	Description
`prefix`	No	Optional prefix added to imported resource names
`workspace`	No	Optional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.
`bundle_json`	Yes	Project bundle JSON from whodb_platform_bundle_export or resources export
`rename_conflicts`	No	Create unique names for resources that conflict with existing resources
`overwrite_conflicts`	No	Update resources that conflict with existing resources

Output Schema

Name	Required	Description
`error`	No
`scope`	No
`status`	No
`warning`	No
`commands`	No
`recovery`	No
`retryable`	No
`workspace`	No	Optional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.
`error_code`	No
`next_steps`	No
`request_id`	No
`result_json`	No
`setup_status`	No
`suggested_tools`	No
`confirmation_token`	No
`confirmation_action`	No
`confirmation_expiry`	No
`confirmation_preview`	No
`idempotency_replayed`	No
`confirmation_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.136.0Oct 23, 2026
- changedOutput schema / properties / recovery / type
```
Previous value: -[
-  "null",
-  "object"
-]New value: +"object"
```
- changedOutput schema / properties / suggested_tools / type
```
Previous value: -[
-  "null",
-  "array"
-]New value: +"array"
```
Addedv0.135.0Oct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the bar is lower. The description still adds non-obvious behavior: default mode is a preview that returns a confirmation token, and confirm must wait for user approval. It does not describe what happens on conflict by default or the failure mode when rename_conflicts and overwrite_conflicts are both set, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose then the plan/confirm workflow, then the option list and workspace targeting. Nothing is wasted, though the parameter enumeration in sentence four is largely redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, multi-option, nested-workspace mutation with an output schema and rich annotations, the description covers the critical workflow: preview default, confirmation token, user approval gate, and target resolution. The only omission is conflict-resolution precedence, which the agent must infer from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters, including the nested workspace fields, are already documented in structured data. The description only restates them ("Supports prefix, rename_conflicts, and overwrite_conflicts", workspace targeting "without changing defaults") without adding format, mutual-exclusivity, or interaction semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Import a project bundle into the selected hosted project") and implicitly distinguishes itself from the sibling read-only operations whodb_platform_bundle_export and whodb_platform_bundle_diff. An agent can tell it apart from whodb_platform_bundle_import_plan, which it explicitly names as a predecessor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing rules: "Use whodb_platform_bundle_import_plan first when possible" and "do not call whodb_platform_confirm until the user approves the import preview." It names the alternatives (plan, confirm) and the condition that gates each, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server