Skip to main content
Glama

contentful_list_entries

Read-onlyIdempotent

List Contentful entries with optional filtering by content type or full-text query; set limit, space, environment, and access token to retrieve entries.

Instructions

List Contentful entries, optionally filtered by content_type or full-text query.

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": {
      "access_token": "<access_token>"
    },
    "name": "contentful_list_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEntries to return (max 100, default 25)
queryNoFull-text search query
space_idNoContentful space id (can be a saved default)
environmentNoEnvironment (default master)
access_tokenYesContentful Content Delivery API token
content_typeNoFilter to one content type id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the filtering behavior but says nothing about pagination, space/environment scoping, or auth needs beyond what the schema provides.

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?

A single, front-loaded sentence with no filler. It is efficient, though it could carry a bit more guidance without loss of clarity.

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

Completeness3/5

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

For a 6-parameter listing tool with full schema coverage and annotations, the description is adequate but thin: it omits return format, pagination behavior (limit exists), and space/environment defaults, leaving the agent to rely entirely on the schema.

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 all six parameters (limit, query, space_id, environment, access_token, content_type) are already documented. The description merely restates content_type and query at a high level without adding syntax or format detail, so 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?

States a specific verb 'List' and resource 'Contentful entries', plus the two filter axes. It implicitly distinguishes itself from contentful_get_entry (single) by being a listing tool, though it does not name siblings explicitly.

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 phrase 'optionally filtered by content_type or full-text query' implies usage contexts, but there is no explicit when-to-use guidance and no reference to the alternative contentful_get_entry for single-entry retrieval.

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

Deploy Server

Other Tools