Skip to main content
Glama

things_get_list

Retrieve all to-dos from a specific Things 3 list by name, such as inbox, today, or upcoming, with optional result limits.

Instructions

Get all to-dos from a specific list by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYes
max_resultsNoLimit number of results returned (defaults to all if not specified)

Implementation Reference

  • The execute method handles the 'things_get_list' tool by mapping the requested list name to an AppleScript filename and then executing it.
    async execute(toolName: string, params: GetParams): Promise<string> {
      let scriptName: string;
      
      // Handle the get_list tool separately
      if (toolName === 'things_get_list') {
        const listParams = params as z.infer<typeof GetListByNameSchema>;
        scriptName = this.listNameToScript[listParams.list];
        if (!scriptName) {
          throw new Error(`Unknown list: ${listParams.list}`);
        }
      } else {
        scriptName = this.scriptMap[toolName];
        if (!scriptName) {
          throw new Error(`Unknown tool: ${toolName}`);
        }
      }
      
      let scriptArgs: string[] = [];
      const options = { maxResults: (params as any).max_results };
      
      // Handle specific tools that need arguments
      if (toolName === 'things_get_project') {
        const projectParams = params as z.infer<typeof GetProjectSchema>;
        scriptArgs = [projectParams.project_id];
      } else if (toolName === 'things_get_area') {
        const areaParams = params as z.infer<typeof GetAreaSchema>;
        scriptArgs = [areaParams.area_id];
      } else if (toolName === 'things_get_todo_details') {
        const todoParams = params as z.infer<typeof GetTodoDetailsSchema>;
        scriptArgs = [todoParams.id];
        // Don't pass maxResults for todo details since it's a single item
        delete options.maxResults;
      }
      
      const output = await executeAppleScriptFile(scriptName, scriptArgs, options);
  • src/tools/get.ts:72-75 (registration)
    Registration of the 'things_get_list' tool within the GetToolHandler class definitions.
      name: 'things_get_list',
      description: 'Get all to-dos from a specific list by name',
      schema: GetListByNameSchema
    },
Behavior2/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 states 'Get all to-dos' but does not clarify return format, pagination behavior, or whether results include completed items. The presence of max_results suggests result limiting, but the description doesn't explain truncation behavior.

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?

Single sentence that is front-loaded and efficient. However, extreme brevity contributes to the lack of behavioral and contextual information needed for a tool with many siblings and no output schema.

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

Completeness2/5

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

Given the complexity of 16+ sibling tools with overlapping functionality, no annotations, and no output schema, the description is insufficient. It omits critical context about the relationship to specific list getters and provides no hint about the return structure.

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 coverage is 50% (max_results has description, list does not). The description adds 'by name' which loosely clarifies the list parameter accepts string identifiers, but doesn't explain the enum values (inbox, today, etc.) or their semantics. Baseline score appropriate given schema partially documents parameters.

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?

The description uses a specific verb ('Get') and resource ('to-dos') and identifies the targeting mechanism ('by name' referring to the list parameter). However, it fails to distinguish this generic getter from sibling-specific tools like things_get_inbox or things_get_today which duplicate functionality for individual lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this tool versus the numerous specific list getters (things_get_inbox, things_get_today, etc.). The agent cannot determine whether to use the generic tool with list='inbox' or the specific things_get_inbox tool.

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/hildersantos/things-mcp'

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