Skip to main content
Glama
thefactremains

Just Claude Things

List Things 3 Todos

things3_get_todos
Read-onlyIdempotent

List todos from Things 3 with filters for status, project, area, tag, or search text. Supports pagination with limit and offset.

Instructions

List todos from Things 3 with optional filters and pagination.

Returns todos matching the specified criteria. Use "status" to filter by list (inbox, today, upcoming, anytime, someday, logbook). Combine with projectId, areaId, tag, or search filters to narrow results.

Args:

  • status: Filter by Things 3 list name

  • projectId: Filter by project ID (get IDs from things3_get_projects)

  • areaId: Filter by area ID (get IDs from things3_get_areas)

  • tag: Filter by tag name (get names from things3_get_tags)

  • search: Case-insensitive substring match against title and notes

  • limit: Max results to return (default 50, max 200)

  • offset: Number of results to skip for pagination (default 0)

Returns: { items: Todo[], total_available, offset, limit, has_more }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by tag name
limitNoMax results to return (default 50)
areaIdNoFilter by area ID
offsetNoNumber of results to skip for pagination
searchNoCase-insensitive substring match against title and notes
statusNoFilter by Things 3 list
projectIdNoFilter by project ID
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds pagination behavior (default limit, max, offset, has_more) and search semantics (case-insensitive substring). No contradictions.

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?

Concise yet informative. Opens with a clear summary, then a paragraph on usage, followed by a structured list of parameters. Every sentence adds necessary detail without redundancy.

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?

For a tool with 7 optional parameters and no output schema, the description covers all key aspects: filtering, pagination, return format, and how to get related IDs. It fully equips an agent to use the 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%, but description adds value by explaining how to obtain IDs from related tools (things3_get_projects, etc.) and clarifying search is case-insensitive substring. This helps an agent use parameters correctly.

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 'List todos from Things 3' with optional filters and pagination. It distinguishes from sibling tools like things3_get_todo (single todo) and things3_create_todo, etc.

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?

Provides clear guidance on when to use each filter and references sibling tools for getting IDs (things3_get_projects, things3_get_areas, things3_get_tags). Does not explicitly state when not to use this tool, but that is implied by sibling names.

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/thefactremains/just-claude-things'

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