Skip to main content
Glama

contentrain_content_list

Read-onlyIdempotent

List content entries in a chosen locale with publish status and dates from meta to review, filter, and audit content without editing files.

Instructions

List content entries (read-only). Each entry carries its publish state under "meta" — status, plus publish_at/expire_at when set — read from the listed locale's meta; singletons and dictionaries carry it at the top level. Local and remote sessions return the same shape. Change status with contentrain_content_status. Returns data from .contentrain/ — do NOT manually create or modify content files.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries to return
modelYesModel ID
filterNoFilter criteria (collection only)
localeNoLocale code (defaults to config default)
offsetNoSkip N entries
resolveNoResolve relation fields to actual data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: the publish-state shape under "meta" (status, publish_at, expire_at), the top-level placement for singletons and dictionaries, and that local and remote sessions return identical shapes. It says nothing about pagination semantics for limit/offset, which is the main remaining gap.

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

Conciseness4/5

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

Front-loads the read-only listing purpose, then layers meta shape, session parity, and the sibling pointer. Every sentence carries information, though the meta-placement clauses are dense and could be tighter.

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?

With no output schema, the description usefully describes the returned entry shape and meta placement, and covers the source-of-truth constraint. The gap is the free-form filter object, whose accepted operators or field syntax are not described anywhere, for a tool with six parameters including a nested object.

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 coverage is 100%, so the schema already documents all six parameters and the baseline is 3. The description adds only marginal meaning — locale determines whose "meta" is read, and the note about singletons/dictionaries hints that filtering applies to collections — but never explains filter criteria syntax, which is the one param the schema leaves as a free-form object.

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?

States a specific verb+resource ("List content entries") and immediately marks it read-only. It also explicitly distinguishes itself from the sibling that mutates state by naming contentrain_content_status as the tool for status changes.

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 clear routing rule for status changes (use contentrain_content_status) and a prohibitive rule (do not manually create or modify files under .contentrain/). It does not discuss when to prefer content_save, describe, or scan, so exclusions beyond the status case are left implicit.

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