Skip to main content
Glama
Contentrain

Contentrain MCP

Official
by Contentrain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

contentrain_bulk

Batch update content entries: copy locales, change statuses, or delete entries, with dry-run preview to see exact changes before committing.

Instructions

Batch operations on content entries. All operations are auto-committed to git. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesModel ID
slugsNoDocument slugs for update_status (document models) — a document is addressed by slug, the same identity contentrain_content_save uses, not by entry ID
localeNoScope update_status to a single locale (i18n models only; defaults to every supported locale)
statusNoNew status for update_status
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 update_status (collection models) or delete_entries
operationYes
source_localeNoSource locale for copy_locale operation
target_localeNoTarget locale for copy_locale operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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"
+}
  3. 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"
+}
  4. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations are largely uninformative (readOnly false, destructive false), so the description carries the burden and does so well: it discloses that every operation auto-commits to git, that dry-run uses a throwaway worktree, that nothing is committed in preview, and that no branch survives. This is exactly the behavioral context an agent needs before mutating content.

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?

Three compact sentences, each earning its place: what the tool is, the git side effect, and the recommended preview workflow. The critical dry-run caveat is front-loaded before the execution guidance.

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 10-parameter mutating tool with no output schema, the description covers the key workflow and side effects. It does not over-explain because the schema documents confirm, locale, slugs, and enums; a small gap is that the description does not spell out the delete confirmation guard, but the schema covers it.

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 90%, so the schema already documents the parameters thoroughly. The description adds no parameter-level meaning beyond framing dry_run as the preview mode, which the schema also states; baseline 3 is appropriate.

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

Purpose4/5

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

States a clear resource ('content entries') and that it performs batch operations, with operation type enumerated in the schema (copy_locale, update_status, delete_entries). It is distinguishable from the single-entry sibling tools by the word 'Batch', though it does not explicitly name those alternatives.

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

Usage Guidelines4/5

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

Gives a concrete workflow: preview with dry_run:true, review counts, then call again to execute. It does not explicitly contrast with single-entry tools or state when not to use it, but the batch/dry-run guidance is clear enough for correct invocation.

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

Deploy Server

Other Tools