Skip to main content
Glama
edricgsh

Readwise Reader MCP Server

by edricgsh

readwise_update_document

Update document metadata in Readwise Reader including title, author, summary, category, location, and publication details to maintain organized reading collections.

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 handleUpdateDocument function implements the core logic of the readwise_update_document tool by calling the Readwise client's updateDocument method.
    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,
          },
        ],
      };
    }
  • Input schema and metadata for the readwise_update_document tool, defining parameters, types, and requirements.
    {
      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,
      },
    },
  • Registration in the tool dispatch switch statement, routing calls to the handleUpdateDocument handler.
    case 'readwise_update_document':
      return handleUpdateDocument(args);
  • src/index.ts:24-26 (registration)
    MCP server registration providing the tools list (including this tool's schema) via ListTools handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:28-32 (registration)
    MCP server CallTool handler that invokes the tool dispatcher.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        return await handleToolCall(name, args);
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 'Update' implies mutation, it doesn't specify permission requirements, whether changes are reversible, rate limits, or what happens to fields not mentioned. This leaves significant gaps for a mutation tool with 8 parameters.

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 and front-loaded with 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 mutation tool with 8 parameters and no annotations or output schema, the description is inadequate. It doesn't address behavioral aspects like permissions, side effects, or response format, leaving the agent with insufficient context for safe and effective use.

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 all 8 parameters thoroughly with descriptions and enums. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high schema coverage.

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 ('Update') and resource ('a document in Readwise Reader'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'readwise_save_document' which might have overlapping functionality, preventing a perfect score.

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. There's no mention of prerequisites, when-not-to-use scenarios, or how it differs from sibling tools like 'readwise_save_document' or 'readwise_delete_document'.

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