Skip to main content
Glama

get_shopping_list

Retrieve structured shopping list tasks from Todoist projects to view items, priorities, due dates, and labels in JSON format.

Instructions

Get all tasks from the "Shopping list" project in Todoist. Returns structured JSON data with task details including id, content, description, priority, due date, labels, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'get_shopping_list' tool. It calls getShoppingList() from task-retrieval service and returns the result as formatted JSON text content.
    export const getShoppingListTool: Tool = {
      schema: {
        name: 'get_shopping_list',
        description:
          'Get all tasks from the "Shopping list" project in Todoist. Returns structured JSON data with task details including id, content, description, priority, due date, labels, and more.',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing get_shopping_list...');
        const result = await getShoppingList();
        console.error('get_shopping_list completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • The schema definition for the 'get_shopping_list' tool, including name, description, and empty input schema (no parameters).
    schema: {
      name: 'get_shopping_list',
      description:
        'Get all tasks from the "Shopping list" project in Todoist. Returns structured JSON data with task details including id, content, description, priority, due date, labels, and more.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Registers the getShoppingListTool.handler in the toolsWithoutArgs registry for handling tool call requests.
    get_shopping_list: getShoppingListTool.handler,
  • src/index.ts:111-111 (registration)
    Registers the tool schema in the ListToolsRequest handler to advertise the 'get_shopping_list' tool.
    getShoppingListTool.schema,
  • The core helper function that fetches tasks from the Todoist 'Shopping list' project using a filter and transforms them into TasksResponse format.
    export async function getShoppingList(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `##${ProjectNames.SHOPPING_LIST}`,
        'get tasks from Shopping list project'
      );
    }
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 mentions the return format ('structured JSON data') and some fields included, which adds value. However, it lacks details on permissions, rate limits, error handling, or whether it's a read-only operation (implied by 'Get' but not confirmed). For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 two sentences that efficiently convey the core action and return details without any fluff. It's front-loaded with the main purpose and follows up with useful return information. Every sentence earns its place by adding value, making it appropriately sized and well-structured.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It covers the purpose and return format, which is sufficient for a basic read operation. However, without annotations or output schema, it could benefit from more behavioral context (e.g., read-only confirmation, error cases) to be fully complete for an agent.

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 the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Since there are no parameters to explain, the baseline is 4, as the description doesn't need to compensate for any schema gaps.

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 clearly states the verb ('Get') and resource ('all tasks from the "Shopping list" project in Todoist'), making the purpose specific and understandable. It distinguishes itself from siblings by focusing on a specific project rather than general task retrieval or other operations. However, it doesn't explicitly contrast with similar tools like 'get_tasks_with_label' or 'search_tasks', which slightly limits differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools for task retrieval (e.g., 'get_tasks_due_tomorrow', 'search_tasks'), there's no indication of when this specific project-focused tool is preferred, nor any prerequisites or exclusions mentioned. Usage is implied by the project name but not explicitly defined.

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