Skip to main content
Glama
Contentrain

Contentrain MCP

Official
by Contentrain
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

contentrain_content_save

Idempotent

Save content entries across all model types, with media paths automatically normalized to public URLs and changes auto-committed to git.

Instructions

Save content entries. Entry format varies by model kind: DICTIONARY — provide "locale" and "data" (flat key-value, all string values); "id" and "slug" are ignored; data keys are the identities. COLLECTION — provide "locale" and "data"; "id" is optional (auto-generated if omitted); "slug" is ignored. DOCUMENT — provide "slug" (required), "locale", and "data"; use the "body" key inside data for markdown content. SINGLETON — provide only "locale" and "data". MEDIA FIELDS (image/video/file): for a media-library asset, pass its storage path ("media/...") or URL; in cloud mode these are automatically normalized to absolute public delivery URLs on save (in markdown bodies too), so saved content renders in a browser anywhere with no SDK — in local mode the relative path is kept as-is. For external images (e.g. a CDN or Unsplash URL), pass the URL directly; it is saved untouched. Changes are auto-committed to git — do NOT manually edit .contentrain/ files after calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesModel ID
entriesYesContent entries to save

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv1.0.33
    • changedInput schema / properties / entries / items / properties / expire_at / description
      Previous value: -"ISO 8601 date for scheduled expiry (stored in meta, must be after publish_at)"New value: +"Scheduled expiry, ISO 8601, must be after publish_at. Same rules as publish_at: meta only, never changes status, null clears, omit leaves unchanged."
    • changedInput schema / properties / entries / items / properties / expire_at / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / entries / items / properties / publish_at / description
      Previous value: -"ISO 8601 date for scheduled publishing (stored in meta)"New value: +"Scheduled publish date, ISO 8601. Stored in meta only — never in the content file — and it does NOT change status: a draft stays a draft, and a published entry is delivered only once this date has passed. Publish with contentrain_bulk update_status. Pass null to clear a previously set date; omit to leave it unchanged."
    • changedInput schema / properties / entries / items / properties / publish_at / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description richly discloses behavior beyond the annotations: ignored fields per model kind, auto-commit to git, media path normalization in cloud vs local mode, and a warning not to manually edit .contentrain/ files. This aligns with readOnlyHint=false and adds substantial operational context.

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 long but densely structured: it front-loads the core action, then uses label-led sections for each model kind and media handling. Every sentence adds necessary operational detail, especially the git auto-commit warning.

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 tool with no output schema, the description is remarkably complete: it specifies required and ignored fields per model kind, media handling rules, cloud/local differences, and a post-save warning. Nothing needed to invoke the tool correctly is missing.

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

Parameters5/5

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

Although schema coverage is 100%, the description goes far beyond the schema by explaining how 'data', 'id', 'slug', and 'locale' behave differently by model kind, how media fields should be passed, and how cloud mode transforms paths. This adds meaning the input schema alone does not convey.

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 opens with the specific verb-resource pair 'Save content entries' and then enumerates the model-kind-specific behaviors. This clearly distinguishes content_save from sibling tools like contentrain_content_list and contentrain_content_delete.

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

Usage Guidelines3/5

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

The intended usage is implied by 'Save content entries' and the detailed per-model instructions, but the description never explicitly contrasts it with sibling tools such as contentrain_bulk or contentrain_model_save. It gives clear context for how to call it, but no explicit when-not-to-use or alternative-selection guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Contentrain/ai'

If you have feedback or need assistance with the MCP directory API, please join our Discord server