Skip to main content
Glama

list_entries

Read-only

Retrieve tasks, notes, and events from Bullet. Use preset views for inbox or overdue items, or query by date period with filters. Paginated results support cursor for next page.

Instructions

List tasks, notes, and events from Bullet. Two modes: (1) use 'view' for presets (inbox=unscheduled, overdue=past-due), or (2) use period+date for calendar queries. Each mode has different valid filters — see parameter descriptions. Returns paginated results; use cursor for next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by tag ID. Pass an array to match any. Works with view=overdue or without a view. Not valid with view=inbox. Use list_tags to find IDs.
dateNoAnchor date for period queries. Format must match period: YYYY-MM-DD for day/week, YYYY-MM for month, YYYY for year. Defaults to current date if omitted. Cannot be used with a view.
kindNoFilter by entry type. Pass an array to match any. Works with view=inbox or without a view. Not valid with view=overdue.
viewNoPreset view. 'inbox' = unscheduled entries (supports status, kind filters). 'overdue' = past-due tasks (supports collection, tag filters). Omit to query by period/date instead.
limitNoMax entries to return (1-200, default 50).
cursorNoPagination cursor from a previous list_entries response. Pass this to get the next page.
expandNoInclude related objects in the response. 'collection' inlines the collection object, 'tags' inlines tag objects. Pass an array for both.
periodNoTime granularity for date-based queries. Cannot be used with a view. If date is set, period controls its scope (day=single day, week=that week, etc). Defaults date to now if omitted.
statusNoFilter by task status. Pass an array to match any. Works with view=inbox or without a view. Not valid with view=overdue.
collectionNoFilter by collection ID. Pass an array to match any. Works with view=overdue or without a view. Not valid with view=inbox. Use list_collections to find IDs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorYes
entriesYes
has_moreYes
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses pagination behavior ('Returns paginated results; use cursor for next page') and mode-dependent filter constraints. It adds useful behavioral context without contradicting annotations.

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?

The description is concise, front-loaded with purpose, and efficiently explains modes and pagination in three sentences. Every sentence adds value with no redundancy.

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?

Given the complexity of 10 parameters and two modes, the description effectively summarizes core behavior and directs users to parameter descriptions. It also mentions pagination and assumes output schema covers return format, making it complete enough for most invocation scenarios.

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?

The input schema already has 100% description coverage, so the tool description pointing to parameter descriptions is sufficient. It does not add extra parameter meaning beyond the schema, but also does not need to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists tasks, notes, and events from Bullet, using specific verbs and resource types. It distinguishes from siblings like list_collections and list_tags by focusing on entries, and outlines two distinct query modes.

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?

The description provides clear guidance on when to use 'view' presets vs. period+date calendar queries, and mentions that filters vary by mode. It does not explicitly name alternatives among siblings, but the mode explanation gives sufficient context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davebream/bullet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server