Skip to main content
Glama

cozi_remove_item

Delete items from Cozi shopping and todo lists using list and item IDs. This action permanently removes selected items from your family organizer lists.

Instructions

Remove/delete an item from a Cozi list. This permanently deletes the item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYesThe ID of the item to remove
listIdYesThe ID of the list containing the item

Implementation Reference

  • The handler for the 'cozi_remove_item' tool inside the executeTool function. It calls CoziClient.removeItem with list_id and item_id, then returns a success message.
    case 'cozi_remove_item': {
      await client.removeItem(args.list_id, args.item_id);
      return {
        success: true,
        message: 'Item removed from list',
      };
    }
  • Input schema definition for the cozi_remove_item tool, specifying list_id and item_id as required string parameters.
    inputSchema: {
      type: 'object',
      properties: {
        list_id: {
          type: 'string',
          description: 'The ID of the list containing the item',
        },
        item_id: {
          type: 'string',
          description: 'The ID of the item to remove',
        },
      },
      required: ['list_id', 'item_id'],
    },
  • src/tools.ts:59-76 (registration)
    Registration of the cozi_remove_item tool in the COZI_TOOLS array, including name, description, and input schema.
    {
      name: 'cozi_remove_item',
      description: 'Remove an item from a Cozi list',
      inputSchema: {
        type: 'object',
        properties: {
          list_id: {
            type: 'string',
            description: 'The ID of the list containing the item',
          },
          item_id: {
            type: 'string',
            description: 'The ID of the item to remove',
          },
        },
        required: ['list_id', 'item_id'],
      },
    },
  • The CoziClient.removeItem method, which performs the actual API DELETE request to remove the specified item from the list.
    async removeItem(listId: string, itemId: string): Promise<void> {
      await this.request(`/${this.accountId}/list/${listId}/item/${itemId}`, {
        method: 'DELETE',
      });
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the deletion is 'permanent,' which is crucial context beyond the basic action. However, it doesn't cover other behavioral aspects like error conditions, permissions required, or response format.

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 short sentences that are front-loaded and waste no words. Every part of the text earns its place by clarifying the action and its permanence.

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 complexity (a destructive operation with 2 parameters) and no annotations or output schema, the description is minimally complete. It covers the permanent nature of the action but lacks details on error handling, permissions, or return values, leaving gaps for an AI agent.

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?

Schema description coverage is 100%, so the schema already documents both parameters (itemId and listId) adequately. The description adds no additional meaning or context about the parameters beyond what the schema provides, such as format examples or relationship details.

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 specific action ('Remove/delete') and resource ('an item from a Cozi list'), distinguishing it from siblings like cozi_mark_item_complete or cozi_edit_item. It uses precise verbs that indicate a destructive operation rather than modification.

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 like cozi_edit_item or cozi_mark_item_complete. It doesn't mention prerequisites, such as needing to retrieve item IDs first, or exclusions, such as not using it for temporary removal.

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/BrandCast-Signage/cozi-mcp-server'

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