Skip to main content
Glama

list_entries

Browse paginated entries for a Strapi content type and retrieve document IDs for get, update, or delete operations; single types return the entry directly.

Instructions

List entries for a content type. For collection types (News Articles, Products, Categories), returns a paginated list with document IDs. For single types (Home Page, About Page), returns the single entry directly. Use this to browse existing content or find document IDs for get/update/delete operations.

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": {
      "content_type": "<content_type>"
    },
    "name": "list_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
localeNoLocale code, e.g. "en", "uk", "da"
page_sizeNoItems per page (default 10)
content_typeYesContent type UID, e.g. "api::news-article.news-article"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the non-obvious branching return behavior (paginated list with IDs vs a single entry). However, it says nothing about authentication/session requirements, pagination limits, or error behavior when a content_type does not exist, which are real unknowns for a no-annotation tool.

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?

Three sentences, front-loaded with the core action, then the two return modes, then the usage guidance. Every sentence adds distinct information with no restatement of the tool name or filler.

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?

There is no output schema, and the description compensates by explaining what comes back in each mode, so an agent knows whether to expect a document ID list or a single entry. Missing pieces are auth expectations and pagination bounds, which are minor for a straightforward read 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 content_type, page, page_size, and locale are already documented in the schema. The description only hints at paging ("paginated list") and adds no format or constraint detail beyond the structured fields, so the baseline 3 applies.

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 gives a specific verb+resource ("List entries for a content type") and goes further by splitting behavior into collection types vs single types, which an agent can act on without opening the schema. It differentiates from get/update/delete by positioning itself as the ID-discovery step, though it does not clarify the overlap with get_entry for single types.

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?

"Use this to browse existing content or find document IDs for get/update/delete operations" gives a clear positive usage context and a downstream-workflow rationale. There are no explicit exclusions (e.g., "use get_entry instead when you already have a document ID"), which keeps it short of a 5.

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