Skip to main content
Glama

contentrain_bulk

Destructive

Copy a locale or delete multiple collection entries in batch, with a dry-run preview before changes are auto-committed to git.

Instructions

Batch operations on content entries: copy a locale, or delete many collection entries. All operations are auto-committed to git. To publish or change status, use contentrain_content_status. DRY RUN (dry_run:true): runs the whole operation in a throwaway worktree and reports exactly what would change — nothing is committed and no branch survives. Recommended workflow: preview with dry_run:true, review the counts, then call again to execute.

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": {
      "operation": "<operation>",
      "model": "<model>"
    },
    "name": "contentrain_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel ID
confirmNoMust be true for delete_entries (not needed while dry_run:true — a preview deletes nothing)
dry_runNoPreview mode: perform the operation in a throwaway worktree and report what would change, committing nothing. Defaults to false so existing callers keep executing.
entry_idsNoEntry IDs for delete_entries (collection models)
operationYes
source_localeNoSource locale for copy_locale operation
target_localeNoTarget locale for copy_locale operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.63
    • changedInput schema / properties / entry_ids / description
      Previous value: -"Entry IDs for update_status (collection models) or delete_entries"New value: +"Entry IDs for delete_entries (collection models)"
    • removedInput schema / properties / locale
      Removed value: -{
      -  "description": "Scope update_status to a single locale (i18n models only; defaults to every supported locale)",
      -  "type": "string"
      -}
    • changedInput schema / properties / operation / enum
      Previous value: -[
      -  "copy_locale",
      -  "update_status",
      -  "delete_entries"
      -]New value: +[
      +  "copy_locale",
      +  "delete_entries"
      +]
    • removedInput schema / properties / slugs
      Removed value: -{
      -  "description": "Document slugs for update_status (document models) — a document is addressed by slug, the same identity contentrain_content_save uses, not by entry ID",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / status
      Removed value: -{
      -  "description": "New status for update_status",
      -  "enum": [
      -    "draft",
      -    "in_review",
      -    "published",
      -    "rejected",
      -    "archived"
      -  ],
      -  "type": "string"
      -}
  2. Changed2 schema fields changedv1.0.35
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for delete_entries"New value: +"Must be true for delete_entries (not needed while dry_run:true — a preview deletes nothing)"
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "Preview mode: perform the operation in a throwaway worktree and report what would change, committing nothing. Defaults to false so existing callers keep executing.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changedv1.0.33
    • addedInput schema / properties / slugs
      Added value: +{
      +  "description": "Document slugs for update_status (document models) — a document is addressed by slug, the same identity contentrain_content_save uses, not by entry ID",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  4. Changed2 schema fields changedv1.0.25
    • changedInput schema / properties / entry_ids / description
      Previous value: -"Entry IDs for update_status or delete_entries"New value: +"Entry IDs for update_status (collection models) or delete_entries"
    • addedInput schema / properties / locale
      Added value: +{
      +  "description": "Scope update_status to a single locale (i18n models only; defaults to every supported locale)",
      +  "type": "string"
      +}
  5. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds substantive context they don't carry: operations are auto-committed to git, dry_run executes in a throwaway worktree where nothing is committed and no branch survives, and confirm is unnecessary during preview. These are exactly the side-effect details an agent needs before invoking a destructive bulk tool.

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

Conciseness5/5

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

Purpose is front-loaded in the opening clause, followed by commit behavior, the alternative tool, dry-run semantics, and the workflow. Every sentence delivers distinct information with no repetition of the schema, and the em-dash construction keeps the dry-run explanation tight.

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

Completeness5/5

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

For a 7-parameter destructive tool with no output schema, the description covers what an agent needs: what the operations do, that changes are git-committed, how to preview safely, and what a preview reports ('review the counts'). Nothing required to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 86%, so the schema already documents most parameters and the baseline is 3. The description still adds meaning beyond it, clarifying that dry_run previews nothing gets committed and that the preview-then-execute workflow applies, which complements the per-parameter notes without fully re-explaining each field.

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?

The first sentence names a specific verb and resource and enumerates both supported operations ('copy a locale, or delete many collection entries'), which maps directly to the two-value enum. It also names the sibling that handles a different job (contentrain_content_status), so an agent can distinguish it from related tools without opening a schema.

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?

Explicit exclusions and routing are given ('To publish or change status, use contentrain_content_status'), plus a concrete recommended workflow: preview with dry_run:true, review the counts, then call again to execute. The 'when to preview vs when to execute' decision is fully spelled out rather than inferred.

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