Skip to main content
Glama

readwise_update_document

Modify document details in Readwise Reader by updating title, author, summary, category, location, or metadata to keep your reading materials organized and current.

Instructions

Update a document in Readwise Reader

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDocument ID to update
titleNoNew title for the document
authorNoNew author for the document
summaryNoNew summary for the document
published_dateNoNew published date (ISO 8601)
image_urlNoNew image URL for the document
locationNoNew location for the document
categoryNoNew category for the document

Implementation Reference

  • The core handler function that implements the readwise_update_document tool. It extracts the document ID and update data from args, calls the Readwise client's updateDocument method, formats a success response with ID and URL, appends any messages, and returns it in the expected MCP content format.
    export async function handleUpdateDocument(args: any) {
      const client = initializeClient();
      const { id, ...updateData } = args as unknown as { id: string } & UpdateDocumentRequest;
      const response = await client.updateDocument(id, updateData);
    
      let responseText = `Document updated successfully!\nID: ${response.data.id}\nReader URL: ${response.data.url}`;
      
      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 input schema definition for the readwise_update_document tool, specifying parameters like id (required), title, author, summary, etc., with enums for location and category.
    {
      name: 'readwise_update_document',
      description: 'Update a document in Readwise Reader',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Document ID to update',
          },
          title: {
            type: 'string',
            description: 'New title for the document',
          },
          author: {
            type: 'string',
            description: 'New author for the document',
          },
          summary: {
            type: 'string',
            description: 'New summary for the document',
          },
          published_date: {
            type: 'string',
            description: 'New published date (ISO 8601)',
          },
          image_url: {
            type: 'string',
            description: 'New image URL for the document',
          },
          location: {
            type: 'string',
            enum: ['new', 'later', 'shortlist', 'archive', 'feed'],
            description: 'New location for the document',
          },
          category: {
            type: 'string',
            enum: ['article', 'book', 'tweet', 'pdf', 'email', 'youtube', 'podcast'],
            description: 'New category for the document',
          },
        },
        required: ['id'],
        additionalProperties: false,
      },
    },
  • The switch case registration in the main handleToolCall function that routes 'readwise_update_document' calls to the handleUpdateDocument handler.
    case 'readwise_update_document':
      return handleUpdateDocument(args);
  • The import statement that brings in the handleUpdateDocument function from document-handlers.ts (noted as .js in source, likely transpiled). Note: lines 1-6 cover multiple document handlers.
    import { 
      handleSaveDocument, 
      handleListDocuments, 
      handleUpdateDocument, 
Behavior2/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. While 'Update' implies a mutation operation, the description doesn't specify whether this requires authentication, what permissions are needed, whether changes are reversible, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 states the core purpose without unnecessary words. It's appropriately sized for a tool with comprehensive schema documentation and gets straight to the point with zero wasted text.

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 mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what happens after the update, what the response looks like, error conditions, or how this tool relates to other document operations in the system. The agent lacks crucial context for proper tool invocation.

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 input schema has 100% description coverage, with clear parameter documentation including enum values for 'location' and 'category'. The description adds no additional parameter information beyond what's already in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 verb ('Update') and resource ('a document in Readwise Reader'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'readwise_save_document' (which might create documents) or 'readwise_delete_document' (which removes them), missing an opportunity for sibling differentiation.

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 'readwise_save_document' (for creating) or 'readwise_list_documents' (for viewing). There's no mention of prerequisites, error conditions, or typical use cases, leaving the agent with insufficient context for appropriate tool selection.

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/arnaldo-delisio/readwise-mcp-enhanced'

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