Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

list_tasks

Get tasks from Super Productivity by applying filters like title, project, tag, include done, and source to narrow results.

Instructions

Returns tasks from Super Productivity with optional filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFilter by title text (case-insensitive contains)
projectIdNoFilter by project ID
projectNameNoFilter by project name
tagIdNoFilter by tag ID
tagNameNoFilter by tag name
includeDoneNoInclude completed tasks
sourceNoWhich task source to query

Implementation Reference

  • Handler: The 'list_tasks' tool definition. Accepts optional query, projectId/projectName, tagId/tagName, includeDone, and source filters. Resolves name-based IDs via resolveTaskFilterIds, then calls SpClient.getTasks and returns the result.
    server.tool(
      "list_tasks",
      "Returns tasks from Super Productivity with optional filters.",
      {
        query: nonEmptyString.optional().describe("Filter by title text (case-insensitive contains)"),
        projectId: nonEmptyString.optional().describe("Filter by project ID"),
        projectName: nonEmptyString.optional().describe("Filter by project name"),
        tagId: nonEmptyString.optional().describe("Filter by tag ID"),
        tagName: nonEmptyString.optional().describe("Filter by tag name"),
        includeDone: z.boolean().optional().describe("Include completed tasks"),
        source: z.enum(["active", "archived", "all"]).optional().describe("Which task source to query"),
      },
      async ({ query, projectId, projectName, tagId, tagName, includeDone, source }) => {
        const resolved = await resolveTaskFilterIds({ projectId, projectName, tagId, tagName });
        const tasks = await SpClient.getTasks({
          query,
          projectId: resolved.projectId,
          tagId: resolved.tagId,
          includeDone,
          source,
        });
        return ok(tasks);
      }
    );
  • Schema: TypeScript interface defining the ListTasksFilters object used to pass filter options to the API.
    export interface ListTasksFilters {
      query?: string;
      projectId?: string;
      tagId?: string;
      includeDone?: boolean;
      source?: "active" | "archived" | "all";
    }
  • src/index.ts:16-16 (registration)
    Registration: Entry point calls registerTaskTools(server) which registers list_tasks along with all other task tools.
    registerTaskTools(server);
  • Helper: SpClient.getTasks makes the actual HTTP GET request to /tasks with query parameters, returning a parsed array of Task objects.
    getTasks(filters?: ListTasksFilters): Promise<Task[]> {
      return request(
        withQuery("/tasks", {
          query: filters?.query,
          projectId: filters?.projectId,
          tagId: filters?.tagId,
          includeDone: filters?.includeDone,
          source: filters?.source,
        }),
        z.array(TaskSchema)
      );
    },
Behavior2/5

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

No annotations provided, so the description carries the full burden. It only states 'returns tasks' without disclosing default behavior, pagination, sorting, or read-only nature. Minimal behavioral context.

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, front-loaded, no unnecessary words. Could be slightly more informative without losing conciseness.

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?

With 7 optional parameters and no output schema or annotations, the description is too minimal. Lacks details on default behaviour (e.g., does it return all tasks if no filters?), result limits, or that it is a read operation.

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?

All 7 parameters are described in the input schema. The tool description adds no additional meaning beyond what the schema provides. Baseline score applied due to high schema coverage.

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 it returns tasks with optional filters, specifying the verb and resource. It distinguishes from 'get_task' (single task) and 'search_tasks' (likely more extensive), but does not explicitly contrast with siblings.

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 on when to use this tool versus alternatives like 'search_tasks', or on when not to use it. Lacks context for selection.

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/claus-92/super-productivity-mcp'

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