Skip to main content
Glama
mjucius

Cozi MCP Server

by mjucius

Delete a list

delete_list

Delete a list from your Cozi account by providing its list ID. Returns true on success.

Instructions

Delete a list. Returns true on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes

Implementation Reference

  • The deleteListHandler function that executes the tool logic. Calls client.deleteList(listId) and returns a boolean.
    export async function deleteListHandler(client: CoziClient, listId: string): Promise<boolean> {
      return client.deleteList(listId);
    }
  • The input schema and description for the 'delete_list' tool. Schema uses Zod: { list_id: z.string() }.
    {
      title: 'Delete a list',
      description: 'Delete a list. Returns true on success.',
      inputSchema: { list_id: z.string() },
  • Registration of 'delete_list' tool via server.registerTool, with the handler that calls deleteListHandler.
    server.registerTool(
      'delete_list',
      {
        title: 'Delete a list',
        description: 'Delete a list. Returns true on success.',
        inputSchema: { list_id: z.string() },
      },
      async ({ list_id }) => {
        const result = await deleteListHandler(await getClient(), list_id);
        return { content: [{ type: 'text', text: JSON.stringify(result) }] };
      },
    );
  • The CoziClient.deleteList method which makes an HTTP DELETE request to /list/{listId} and returns true.
    async deleteList(listId: string): Promise<boolean> {
      await this.ensureAuthenticated();
      await this.http.request({
        method: 'DELETE',
        endpoint: this.accountEndpoint(`/list/${listId}`),
      });
      return true;
    }
  • The 'delete_list' entry in the TOOL_NAMES constant array, enumerating all tool names.
    'delete_list',
Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It only states the action and return value, omitting details like permanence of deletion, required permissions, or error scenarios.

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 extremely concise with two sentences, containing no extraneous information. Every word serves a purpose.

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 tool's simplicity, the description is barely adequate. It lacks parameter documentation and does not mention return format or failure modes, which would be expected for a destructive operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage and the tool description adds no meaning to the 'list_id' parameter. The agent is left to infer what 'list_id' is and how to obtain it.

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 that the tool deletes a list and returns true on success. It distinguishes itself from sibling tools like 'delete_appointment' through the resource name.

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 is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, conditions, or alternative tools for similar operations.

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/mjucius/cozi_mcp'

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