Skip to main content
Glama

deleteCollection

Remove a specific collection from Raindrop.io by providing its unique ID. This tool facilitates the management of your bookmark collections, ensuring a clean and organized workspace.

Instructions

Delete a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCollection ID

Implementation Reference

  • Core handler function that executes the deletion of a Raindrop collection by making a DELETE request to the Raindrop API endpoint /collection/{id}.
    /**
     * Delete a collection
     * Raindrop.io API: DELETE /collection/{id}
     */
    async deleteCollection(id: number): Promise<void> {
      await this.client.DELETE('/collection/{id}', {
        params: { path: { id } }
      });
    }
  • Zod input schema for the collection_manage tool, which supports 'delete' operation requiring 'id' for deleteCollection functionality.
    export const CollectionManageInputSchema = z.object({
        operation: z.enum(['create', 'update', 'delete']),
        id: z.number().optional(),
        title: z.string().optional(),
        parentId: z.number().optional(),
    });
  • Declarative registration/configuration of the 'collection_manage' MCP tool, which invokes deleteCollection when operation='delete'.
    const collectionManageTool = defineTool({
        name: 'collection_manage',
        description: 'Creates, updates, or deletes a collection. Use the operation parameter to specify the action.',
        inputSchema: CollectionManageInputSchema,
        outputSchema: CollectionOutputSchema,
        handler: handleCollectionManage,
    });
  • MCP tool handler logic within handleCollectionManage that calls the deleteCollection service method for the delete operation.
            case 'delete':
                if (!args.id) throw new Error('id is required for delete');
                await raindropService.deleteCollection(args.id);
                return { deleted: true };
            default:
                throw new Error(`Unsupported operation: ${String(args.operation)}`);
        }
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention permissions required, whether deletion is permanent or reversible, effects on contained items, or error conditions. For a destructive operation, this lack of transparency is a significant gap.

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 extremely concise with just three words, front-loading the core action. However, it's arguably under-specified rather than efficiently informative, as it omits critical context for a destructive tool. Still, it wastes no words on redundancy.

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 destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address safety, return values, or error handling, leaving the agent with insufficient context to use it correctly. More detail is needed for such a high-stakes 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?

Schema description coverage is 100%, with the single parameter 'id' documented as 'Collection ID'. The description adds no additional meaning beyond this, such as format examples or where to find the ID. Baseline 3 is appropriate since the schema adequately covers parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a collection' clearly states the action (delete) and target (collection), but it's vague about scope and doesn't distinguish from sibling tools like 'deleteBookmark', 'deleteHighlight', or 'emptyTrash'. It provides basic purpose but lacks specificity about what constitutes a collection or deletion consequences.

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 like 'emptyTrash' or 'removeEmptyCollections', nor are prerequisites or constraints mentioned. The description offers no context for selection among deletion-related tools, leaving usage decisions ambiguous.

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

Related 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/adeze/raindrop-mcp'

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