Skip to main content
Glama
edricgsh

Readwise Reader MCP Server

by edricgsh

readwise_delete_document

Remove a document from Readwise Reader by specifying its document ID to manage your reading list and content library.

Instructions

Delete a document from Readwise Reader

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDocument ID to delete

Implementation Reference

  • The handleDeleteDocument function implements the core logic for the readwise_delete_document tool. It initializes the Readwise client, calls deleteDocument(id), handles any messages, and returns a formatted text response.
    export async function handleDeleteDocument(args: any) {
      const client = initializeClient();
      const { id } = args as { id: string };
      const response = await client.deleteDocument(id);
    
      let responseText = `Document ${id} deleted successfully!`;
      
      if (response.messages && response.messages.length > 0) {
        responseText += '\n\nMessages:\n' + response.messages.map(msg => `${msg.type.toUpperCase()}: ${msg.content}`).join('\n');
      }
    
      return {
        content: [
          {
            type: 'text',
            text: responseText,
          },
        ],
      };
    } 
  • The tool definition including name, description, and input schema for validating the document ID parameter.
      name: 'readwise_delete_document',
      description: 'Delete a document from Readwise Reader',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Document ID to delete',
          },
        },
        required: ['id'],
        additionalProperties: false,
      },
    },
  • The switch case in handleToolCall that registers and dispatches to the handleDeleteDocument handler for the 'readwise_delete_document' tool.
    case 'readwise_delete_document':
      return handleDeleteDocument(args);
  • Import statement that brings in the handleDeleteDocument function used by the tool dispatcher.
    import { 
      handleSaveDocument, 
      handleListDocuments, 
      handleUpdateDocument, 
      handleDeleteDocument 
    } from './document-handlers.js';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this is permanent, reversible, requires specific permissions, or has rate limits. It provides minimal context beyond the basic action.

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 a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple deletion operation and front-loads the essential information.

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?

For a destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deletion (success confirmation, error handling), whether the action is permanent, or any authentication requirements. Given the complexity and lack of structured data, more context is needed.

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' clearly documented in the schema as 'Document ID to delete'. The description doesn't add any additional meaning about the parameter beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the action ('Delete') and resource ('a document from Readwise Reader'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'readwise_update_document' or 'readwise_save_document' in terms of when to choose deletion over other document operations.

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. With siblings like 'readwise_update_document' and 'readwise_save_document', there's no indication of when deletion is appropriate versus modification or creation, nor any mention of prerequisites or consequences.

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/edricgsh/Readwise-Reader-MCP'

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