Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

get_projects

Retrieve all projects from Super Productivity, with optional filtering by project title to locate specific ones.

Instructions

Returns all projects in Super Productivity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFilter by project title

Implementation Reference

  • Registration and handler for the get_projects tool. Calls SpClient.getProjects(query) and returns the result.
    export function registerProjectTools(server: McpServer) {
      server.tool(
        "get_projects",
        "Returns all projects in Super Productivity.",
        {
          query: z.string().optional().describe("Filter by project title"),
        },
        async ({ query }) => {
          const projects = await SpClient.getProjects(query);
          return ok(projects);
        }
      );
  • Input schema for get_projects: optional query string to filter by project title.
    {
      query: z.string().optional().describe("Filter by project title"),
  • src/index.ts:17-17 (registration)
    Registration call in the main index.ts that wires up the get_projects tool.
    registerProjectTools(server);
  • The SpClient.getProjects helper that makes the REST API call to GET /projects with optional query filter.
    getProjects(query?: string): Promise<Project[]> {
      return request(
        withQuery("/projects", {
          query,
        }),
        z.array(ProjectSchema)
      );
    },
  • ProjectSchema zod validation schema defining the shape of project objects returned by the API.
    const ProjectSchema = z.object({
      id: z.string(),
      title: z.string(),
      isArchived: z.boolean().default(false),
    }).passthrough();
Behavior2/5

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

With no annotations provided, the description carries full burden. It states 'returns all projects' but gives no details about potential limitations (pagination, ordering, performance) or side effects. For a read operation, the behavioral context is minimal.

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?

The description is a single short sentence, efficiently front-loading the purpose. However, it could be slightly more structured (e.g., listing what is returned).

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 (one optional param, no output schema), the description is adequate but incomplete—it doesn't hint at the response structure or clarify if 'all projects' includes metadata like IDs or timestamps.

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?

The schema has 100% coverage with a single parameter described as 'Filter by project title'. The description adds no further meaning beyond this, meeting the baseline expectation.

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 uses a specific verb 'Returns' and clearly identifies the resource 'projects', effectively distinguishing it from sibling tools which operate on tasks, tags, or status.

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

Usage Guidelines3/5

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

The description implies usage as a simple project listing tool, but provides no guidance on when to use it vs alternatives like search_tasks (which is task-focused). No exclusions or prerequisites are mentioned.

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