ATOMSATOMSDocs
Tool Reference

atoms_bulk_import

Bulk create 1-100 items in a single call

Create up to 100 items in a single request. Each item is processed independently : if one item fails validation, the rest still succeed. This is ideal for AI-generated requirements, batch migrations, or seeding a new project.

In MCP hosts that support rich content, this tool renders an interactive results table with color-coded status indicators for each created item.

Parameters

ParameterTypeRequiredDescription
project_idstring (UUID)YesThe project to import items into
itemsarrayYesArray of 1-100 item objects (see below)

Item Object

FieldTypeRequiredDescription
typestringYesrequirement, test-case, or note
titlestringYesItem title (1-500 characters)
bodystringNoRich text content
summarystringNoBrief summary
domainsstring[]NoDomain tags
levelstringNoSystem, Subsystem, or Component
parent_idstringNoA single parent item ID for auto-linking

Example Response

{
  "status": "success",
  "data": {
    "created": 3,
    "items": [
      { "id": "REQ-015", "type": "requirement", "title": "Encrypt all PII fields" },
      { "id": "REQ-016", "type": "requirement", "title": "Rotate encryption keys quarterly" },
      { "id": "TC-053", "type": "test-case", "title": "Verify PII encryption at rest" }
    ],
    "errors": [
      {
        "index": 3,
        "title": "",
        "error": "Title is required and must be 1-500 characters"
      }
    ]
  }
}

Notes

  • This tool modifies data (readOnlyHint: false, destructiveHint: false).
  • The batch does not abort on individual item failures. Check the errors array to identify any items that were not created.
  • Each successfully created item is logged to change_history independently.
  • Unlike atoms_create_item, the item object uses a singular parent_id field (not parent_ids). Only one parent relationship can be set per item during bulk import.
  • The 100-item limit is enforced server-side. Requests exceeding this limit are rejected before any items are processed.

On this page