Skip to main content
Glama
NomaCMS

NomaCMS MCP Server

Official
by NomaCMS

List Entries

list_entries

Fetch content entries from a collection using advanced filters, sorting, and pagination. Supports powerful 'where' queries for precise results.

Instructions

List content entries for a collection with advanced filtering, sorting, and pagination. Use the 'where' parameter for powerful queries. Read the 'query-reference' resource for full documentation on operators and examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by field:direction, comma-separated for multiple. Examples: 'created_at:desc', 'title:asc,created_at:desc'. Supports core columns (id, created_at, updated_at, published_at) and custom field names.
countNoIf true, return only the count of matching entries: { count: N }
firstNoIf true, return only the first matching entry as a single object instead of an array
limitNoLimit the number of results (ignored if paginate is set)
stateNoFilter by state: 'draft' or 'published'. Defaults to published entries.
whereNoFilter conditions as a nested object. Supports operators: eq, lt, lte, gt, gte, not, like, in, not_in, null, not_null, between, not_between. Simple: { "state": "published" }. With operators: { "price": { "lt": 50 }, "title": { "like": "news" } }. OR group: { "or": [{ "tags": "clearance" }, { "campaign": { "name": "Summer" } }] }. Relation filter: outer key = relation field on this collection; inner keys = field names on the related entry, e.g. { "author": { "name": { "eq": "John" } } }. Core columns (id, uuid, locale, state, created_at, updated_at, published_at) can be filtered directly.
localeNoFilter by locale (e.g. 'en')
offsetNoSkip N results (requires limit to be set)
excludeNoComma-separated field names to exclude from response (e.g. 'content,excerpt')
paginateNoEnable pagination with N items per page. Returns paginated response with meta data. Overrides limit/offset.
collection_slugYesThe collection slug
Behavior3/5

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

No annotations provided, so description carries burden. It implies read-only by listing, but does not explicitly state safety, side effects, or rate limits.

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?

Three sentences are concise and front-loaded with purpose. No wasted words.

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

Completeness2/5

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

No output schema; description lacks details on default return format, pagination structure, and edge cases. Minimal completeness for a complex tool with 11 parameters.

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 covers all parameters, so baseline is 3. The description adds some value by highlighting 'where' and pointing to reference, but does not add significant new meaning beyond the schema.

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?

The description clearly states the tool lists content entries for a collection with advanced features. It distinguishes from siblings like list_assets, but does not explicitly differentiate from get_entry.

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 description guides use of the 'where' parameter and references external docs, but does not explain when to prefer this over alternatives like get_entry.

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/NomaCMS/nomacms-mcp-server'

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