Skip to main content
Glama

list_gtd_projects

Retrieve all GTD projects from Todoist by filtering specific project tags while excluding baby-related tasks. Returns structured JSON with task details including status, priority, due dates, and labels.

Instructions

List all GTD projects from Todoist using the (#Projects | #Brian projects | #Ansonia Projects) & !subtask filter, excluding baby-related projects. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the core logic of the 'list_gtd_projects' tool by invoking listGtdProjects() service and formatting the response as MCP tool output.
      handler: async () => {
        console.error('Executing list_gtd_projects...');
        const result = await listGtdProjects();
        console.error('list_gtd_projects completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • The schema defining the tool's name, description, and input schema (no parameters required).
    schema: {
      name: 'list_gtd_projects',
      description:
        'List all GTD projects from Todoist using the (#Projects | #Brian projects | #Ansonia Projects) & !subtask filter, excluding baby-related projects. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Registration of the tool handler in the toolsWithoutArgs registry using the normalized snake_case name 'list_gtd_projects'.
    list_gtd_projects: listGtdProjectsTool.handler,
  • The core service function that fetches GTD projects from Todoist using a specific filter excluding subtasks and baby projects.
    export async function listGtdProjects(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `(#Projects | #Brian projects | #Ansonia Projects) & !subtask & ${BABY_PROJECTS_EXCLUSION}`,
        'list GTD projects'
      );
    }
  • src/index.ts:107-107 (registration)
    Registration of the tool schema in the MCP server's listTools response.
    listGtdProjectsTool.schema,
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 discloses that the tool returns structured JSON data with specific task details, which is helpful behavioral information. However, it doesn't mention potential limitations like rate limits, authentication requirements, or whether this is a read-only operation (though 'List' implies reading).

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 a single, well-structured sentence that efficiently conveys purpose, filtering criteria, and return format. Every element serves a clear purpose with zero wasted words, making it easy to parse quickly.

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?

For a tool with 0 parameters, no annotations, and no output schema, the description provides good completeness: it explains what the tool does, what filters it applies, and what data it returns. However, it could be more complete by explicitly stating it's a read-only operation or mentioning any authentication context, given the lack of annotations.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not introducing confusion or redundancy.

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 verb ('List') and resource ('all GTD projects from Todoist') with specific filtering criteria (using specific project labels and excluding baby-related projects). It distinguishes itself from sibling tools like 'get_brian_only_projects' or 'get_inbox_projects' by focusing on GTD projects with particular label filters and exclusions.

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 context for when to use this tool: when listing GTD projects with specific label filters (#Projects, #Brian projects, #Ansonia Projects) and excluding baby-related projects. However, it doesn't explicitly state when NOT to use it or name alternatives among the many sibling tools (e.g., 'get_brian_only_projects' for different filtering).

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/bkotos/todoist-mcp'

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