Skip to main content
Glama
Contentrain

Contentrain MCP

Official
by Contentrain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

contentrain_merge

Merge a review-mode branch into the contentrain branch using local git operations. Resolve target by model, locale, or latest commit, and confirm the merge.

Instructions

Merge a review-mode branch into contentrain. Local git operation — no external platform needed. Merges the feature branch into the contentrain branch, advances the base branch via update-ref, selectively syncs .contentrain/ files to the working tree, and prunes the merged branch. Target by exact "branch" name, or resolve by "model" (+ optional "locale"/"latest").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoResolve the branch by model id (e.g. "blog-post").
branchNoExact branch name to merge (e.g. cr/content/blog-post/...). Omit to resolve by model.
latestNoWhen multiple branches match the model, merge the most recently committed one.
localeNoNarrow model resolution to a locale.
confirmYesMust be true to confirm the merge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.21
    • changedInput schema / properties / branch / description
      Previous value: -"Branch name to merge (e.g. cr/normalize/extract/...)"New value: +"Exact branch name to merge (e.g. cr/content/blog-post/...). Omit to resolve by model."
    • addedInput schema / properties / latest
      Added value: +{
+  "description": "When multiple branches match the model, merge the most recently committed one.",
+  "type": "boolean"
+}
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Narrow model resolution to a locale.",
+  "type": "string"
+}
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Resolve the branch by model id (e.g. \"blog-post\").",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "branch",
-  "confirm"
-]New value: +[
+  "confirm"
+]
  2. Addedv0.1.5

TDQS

A3.7/5.0
Behavior1/5

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

The description discloses destructive behavior ('prunes the merged branch'), but the annotations mark destructiveHint as false, creating a contradiction. Additionally, it does not mention side effects like data loss or the need for permissions beyond the contradiction.

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?

The description is two sentences, front-loaded with the primary action, and each sentence adds essential detail without redundancy. No superfluous words.

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

Completeness3/5

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

The description explains the merge process well but lacks mention of return values (since no output schema), prerequisites (e.g., being in a git repo), and error scenarios. For a 5-parameter tool with no output schema, more context on outcome is needed.

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 description coverage is 100%, but the description adds value by explaining the resolution logic between 'branch' and 'model' parameters and emphasizing 'confirm' must be true. This provides clarity beyond the individual parameter descriptions.

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 description clearly states the verb 'merge' and specific resource 'review-mode branch into contentrain' with a detailed breakdown of operations (merge, update-ref, sync, prune). It also distinguishes from sibling tools like contentrain_branch_delete and contentrain_submit by specifying it's a local git operation.

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?

The description explains when to use the tool (merging review-mode branches) and how to target branches either by exact name or by model with optional locale/latest. However, it does not explicitly state when not to use it or mention alternative tools like contentrain_submit.

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