Skip to main content
Glama

List entries

list_entries
Read-only

Read stored RSS/Atom entries in reverse chronological order, with paging, date/feed filters, and unread or starred views.

Instructions

Read stored entries newest-first, with paging and unread/starred filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEntries per page
sinceNoOnly entries published on/after this ISO-8601 date or epoch seconds
offsetNoEntries to skip, for paging
feed_idNoRestrict to one feed
unread_onlyNoOnly entries not yet marked read
oldest_firstNoSort ascending by publication time
starred_onlyNoOnly starred entries

Output Schema

NameRequiredDescriptionDefault
totalNoTotal entries matching the filters
offsetNo
entriesNo
has_moreNoTrue when offset + returned < total
returnedNoEntries in this page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the default newest-first ordering, which is useful context, but everything else it mentions (paging, unread/starred filters) duplicates the schema, and it says nothing about page-size limits or behavior at the end of a feed.

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?

A single sentence with zero filler, and the most important information (read-only listing, default ordering) is front-loaded before the filter modifiers.

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 full parameter coverage, the description only needs to frame the operation, which it does. The minor gap is that feed scoping and the default page size are left entirely to the schema, but nothing an agent needs in order to call this correctly is missing.

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 seven parameters are documented in the schema itself, making 3 the baseline. The description touches paging, unread and starred filters but adds no syntax or format detail, and omits mention of since, feed_id and limit entirely.

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?

"Read stored entries newest-first, with paging and unread/starred filters" gives a concrete verb (read), a concrete resource (stored entries), and the default ordering plus filter dimensions. It implicitly contrasts with search_entries by framing this as a plain listing, but it never names the sibling, so differentiation is soft rather than explicit.

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 description implies browsing/listing as the use case but states no when-to-use or when-not-to-use conditions and names no alternative. An agent must infer that search_entries is for querying and this tool is for enumerating, which is reasonable but not stated.

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