mcp-feed-reader-crunchtools

List Entries Tool

list_entries_tool

Read-only

List feed entries with optional filters for date range, feed, category, and unread status. Paginate to fetch only recent items without paging through everything.

Instructions

List entries with optional filters.

Date-window filters apply to COALESCE(published, created_at), so entries with no publish date still fall in the window by ingest time. Use them to fetch only a trailing period instead of paging through everything.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max entries to return (1-500, default: 50)
`offset`	No	Pagination offset (default: 0)
`feed_id`	No	Filter by feed ID
`since_days`	No	Only entries dated within the last N days (1-366). Mutually exclusive with published_after/published_before.
`category_id`	No	Filter by category ID
`unread_only`	No	Show only unread entries (default: True)
`published_after`	No	Inclusive lower bound, ISO-8601 date or datetime (e.g. "2026-08-23" or "2026-08-23T00:00:00Z").
`published_before`	No	Inclusive upper bound, ISO-8601 date or datetime.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.2.2Sep 27, 2026

changedInput schema / properties / category_id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / feed_id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / published_after

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Inclusive lower bound, ISO-8601 date or datetime\n(e.g. \"2026-08-23\" or \"2026-08-23T00:00:00Z\")."
+}

addedInput schema / properties / published_before

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Inclusive upper bound, ISO-8601 date or datetime."
+}

addedInput schema / properties / since_days

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only entries dated within the last N days (1-366).\nMutually exclusive with published_after/published_before."
+}

First observedv0.1.3Aug 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true; the description goes further by disclosing that date-window filters compare against COALESCE(published, created_at), so undated entries still fall in a window by ingest time. That is real behavioral context an agent could not infer from the annotations or schema, though pagination/ordering behavior is left unstated.

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?

Two short sentences with no filler, and the non-obvious COALESCE caveat is placed immediately after the topic sentence rather than buried. Nothing restates the tool name or the schema.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and all 8 optional parameters are fully documented in the schema. The description's single job — conveying the surprising date-window semantics — is done, and the tool is read-only so no auth or destructive caveats are needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: it explains the actual comparison column used by since_days/published_after/published_before, which changes how an agent interprets those bounds. It does not clarify the interaction between unread_only's true default and the date filters, so it stops short of a 5.

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 and resource ('List entries') plus the fact that filters are optional, so the agent knows the shape of the call. However, it never distinguishes itself from the sibling search_entries_tool, leaving the boundary between plain listing and searching to inference.

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?

It gives one concrete usage instruction — use date-window filters to fetch a trailing period instead of paging through everything — which is genuine guidance for a subset of the call. But there is no when-not guidance and no routing to search_entries_tool, which is the obvious alternative for filtered retrieval, so usage is only partially covered.

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

Deploy Server