Skip to main content
Glama
crunchtools

mcp-feed-reader-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

List Entries Tool

list_entries_tool

List RSS/Atom feed entries with filters for feed, category, unread status, and date windows; fetch a trailing period instead of 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
NameRequiredDescriptionDefault
limitNoMax entries to return (1-500, default: 50)
offsetNoPagination offset (default: 0)
feed_idNoFilter by feed ID
since_daysNoOnly entries dated within the last N days (1-366). Mutually exclusive with published_after/published_before.
category_idNoFilter by category ID
unread_onlyNoShow only unread entries (default: True)
published_afterNoInclusive lower bound, ISO-8601 date or datetime (e.g. "2026-08-23" or "2026-08-23T00:00:00Z").
published_beforeNoInclusive upper bound, ISO-8601 date or datetime.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.2
    • 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."
+}
  2. First observedv0.1.3

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one non-obvious behavioral trait: date filters compare against COALESCE(published, created_at), so undated entries are matched by ingest time. That is real value beyond the schema, but read-only safety, ordering, and paging behavior are 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and then the non-obvious filter semantics. The opening sentence is slightly generic and restates the name, but nothing is padded or duplicated.

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?

With an output schema present and 100% schema description coverage, most of the burden is already lifted. The description closes the main remaining gap (date-window column semantics) but omits ordering, whether unread_only is the significant default it appears to be, and routing versus search_entries_tool.

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. The description goes beyond it by explaining what column published_after/published_before/since_days actually compare against and what happens when published is null — context the schema itself never supplies.

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') with the qualifier 'optional filters', which is immediately distinguishable from mutation siblings like mark_read_tool or delete_feed_tool. It does not, however, differentiate itself from search_entries_tool, which is the nearest ambiguous alternative.

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?

Offers guidance on when to use the date-window filters ('to fetch only a trailing period instead of paging through everything'), which is a genuine usage hint. But it never says when to use this tool instead of search_entries_tool, nor when to prefer since_days over published_after/published_before beyond the mutual-exclusion note buried in the schema.

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