Skip to main content
Glama
edricgsh

Readwise Reader MCP Server

by edricgsh

readwise_save_document

Save web documents or HTML content to Readwise Reader for organized reading and reference, supporting tags, categories, and custom locations.

Instructions

Save a document (URL or HTML content) to Readwise Reader

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the document to save
htmlNoHTML content of the document (optional)
tagsNoTags to add to the document
locationNoLocation to save the document (default: new)
categoryNoCategory of the document (auto-detected if not specified)

Implementation Reference

  • The main handler function for the 'readwise_save_document' tool. It initializes the Readwise client, casts arguments to CreateDocumentRequest, calls client.createDocument(), formats a success response with document details and any messages, and returns it in MCP content format.
    export async function handleSaveDocument(args: any) {
      const client = initializeClient();
      const data = args as unknown as CreateDocumentRequest;
      const response = await client.createDocument(data);
    
      let responseText = `Document saved successfully!\nID: ${response.data.id}\nTitle: ${response.data.title || 'Untitled'}\nURL: ${response.data.url}\nLocation: ${response.data.location}`;
      
      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_save_document' tool, specifying parameters like url (required), html, tags, location, and category with types and descriptions.
    {
      name: 'readwise_save_document',
      description: 'Save a document (URL or HTML content) to Readwise Reader',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'URL of the document to save',
          },
          html: {
            type: 'string',
            description: 'HTML content of the document (optional)',
          },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'Tags to add to the document',
          },
          location: {
            type: 'string',
            enum: ['new', 'later', 'shortlist', 'archive', 'feed'],
            description: 'Location to save the document (default: new)',
          },
          category: {
            type: 'string',
            enum: ['article', 'book', 'tweet', 'pdf', 'email', 'youtube', 'podcast'],
            description: 'Category of the document (auto-detected if not specified)',
          },
        },
        required: ['url'],
        additionalProperties: false,
      },
    },
  • The switch case in the main handleToolCall function that registers and routes 'readwise_save_document' calls to the handleSaveDocument handler.
    case 'readwise_save_document':
      return handleSaveDocument(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. It states the tool saves documents but doesn't mention authentication requirements, rate limits, error conditions, or what happens on success (e.g., whether it returns a document ID). For a write operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 without unnecessary words. It's appropriately sized for a tool with clear functionality and doesn't waste space on redundant information already available in the schema.

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 write operation with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after saving (success indicators, returned data), doesn't mention authentication or error handling, and provides minimal guidance despite rich parameter schema. The description should do more to compensate for the lack of structured metadata.

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 all parameters are documented in the schema. The description adds minimal value beyond the schema by mentioning URL or HTML content, but doesn't provide additional context about parameter interactions (e.g., that html is optional and overrides url if both provided) or practical usage examples. Baseline 3 is appropriate when the schema does most of the work.

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 ('Save') and resource ('a document to Readwise Reader'), specifying it accepts URL or HTML content. It distinguishes from siblings like delete_document and list_documents by focusing on creation rather than modification or retrieval. However, it doesn't explicitly differentiate from update_document which might also involve saving changes.

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 update_document or list_documents. It mentions what the tool does but offers no context about prerequisites, typical use cases, or when other tools might be more appropriate given the sibling set.

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