Skip to main content
Glama

list_entries

Read-only

Retrieve and browse content entries from a Strapi content type with pagination, sorting, and filters. Returns a readable markdown list with metadata and pagination info.

Instructions

List content entries from a Strapi content type with full pagination, sorting, and filtering support. Returns entries formatted as a readable markdown list with metadata and pagination info. Use this to browse and explore content, applying filters and sort orders as needed. Call list_content_types first if you are unsure which content types are available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination, starting at 1
sortNoSort expression (e.g., 'title:asc', 'createdAt:desc', 'price:asc,title:desc')
fieldsNoComma-separated list of fields to return (e.g., 'title,slug,price')
localeNoLocale code to filter entries (e.g., 'en', 'fr', 'de')
statusNoPublication status filter: 'draft' or 'published' (v5 only)
filtersNoJSON string of Strapi filters (e.g., '{"title":{"$contains":"hello"}}' or '{"price":{"$gt":10}}')
populateNoRelations to populate. Use '*' for all, or specify fields like 'author,category'*
page_sizeNoNumber of entries per page (1-100, default 25)
content_typeYesPlural API ID of the content type (e.g., 'articles', 'products', 'categories')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering safety. The description adds context about the output format ('readable markdown list with metadata and pagination info') and capabilities, which enhances transparency beyond annotations.

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 only 4 sentences, with no redundant information. It front-loads the core purpose and efficiently conveys key usage guidance. Every sentence adds value.

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?

Given the tool's complexity (9 parameters, output schema exists), the description covers the main use case and provides a prerequisite hint. However, it could briefly mention navigating pagination or the scope of results, but the output schema fills some gaps. Overall, it feels sufficiently complete for a read-only browsing tool.

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 100%, so the baseline is 3. The description mentions 'full pagination, sorting, and filtering' which maps to parameters, but does not add new meaning beyond the schema details. No parameter-specific elaboration is provided.

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 'List' and the resource 'content entries from a Strapi content type', with specific features (pagination, sorting, filtering). It also distinguishes from siblings by advising to call list_content_types first, and implies its use for browsing vs. other operations.

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 explicitly advises to use list_content_types first when unsure, and states 'Use this to browse and explore content'. However, it does not explicitly mention when not to use this tool, such as for single entry retrieval or complex search queries (compared to get_entry or search_entries).

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/alex2zimmermann-ux/strapi-mcp'

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