Skip to main content
Glama

readwise_create_highlight

Create manual highlights in Readwise to save and organize important text passages from books, articles, podcasts, or tweets with metadata like author, source, and notes.

Instructions

Create new highlights manually in Readwise

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
highlightsYesArray of highlights to create

Implementation Reference

  • The primary handler function that implements the logic for the 'readwise_create_highlight' tool. It initializes the Readwise client and invokes client.createHighlight(args) with the provided arguments, returning the API response as formatted JSON text content.
    export async function handleCreateHighlight(args: any) {
      const client = await initializeClient();
      
      const response = await client.createHighlight(args);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The tool definition object including name, description, and detailed inputSchema for validating parameters to create highlights, such as array of highlights with text (required), title, author, source_url, etc.
      name: 'readwise_create_highlight',
      description: 'Create new highlights manually in Readwise',
      inputSchema: {
        type: 'object',
        properties: {
          highlights: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                text: {
                  type: 'string',
                  description: 'The highlight text (required)',
                },
                title: {
                  type: 'string',
                  description: 'Title of the source book/article',
                },
                author: {
                  type: 'string',
                  description: 'Author of the source',
                },
                source_url: {
                  type: 'string',
                  description: 'URL of the original source',
                },
                source_type: {
                  type: 'string',
                  description: 'Unique identifier for your app/source',
                },
                category: {
                  type: 'string',
                  enum: ['books', 'articles', 'tweets', 'podcasts'],
                  description: 'Category of the source',
                },
                note: {
                  type: 'string',
                  description: 'Personal note or annotation for the highlight',
                },
                location: {
                  type: 'number',
                  description: 'Location in the source (page number, position, etc.)',
                },
                location_type: {
                  type: 'string',
                  enum: ['page', 'order', 'time_offset'],
                  description: 'Type of location reference',
                },
                highlighted_at: {
                  type: 'string',
                  description: 'When the highlight was made (ISO 8601)',
                },
              },
              required: ['text'],
            },
            description: 'Array of highlights to create',
            minItems: 1,
          },
        },
        required: ['highlights'],
        additionalProperties: false,
      },
    },
  • The switch case in the main tool dispatcher that routes 'readwise_create_highlight' calls to the handleCreateHighlight function.
    case 'readwise_create_highlight':
      return handleCreateHighlight(args);
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. It states 'create' which implies a write operation, but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what happens on success (e.g., returns highlight IDs). This is inadequate for a mutation tool with zero annotation coverage.

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 any fluff or redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain behavioral traits like side effects, return values, or error conditions. While the schema covers parameters well, the overall context for safe and effective use is lacking.

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, so parameters are well-documented in the schema itself. The description adds no additional meaning beyond implying an array of highlights is needed, which is already clear from the schema. This meets the baseline score of 3 when schema coverage is high.

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 ('create') and resource ('highlights manually in Readwise'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'readwise_save_document' or 'readwise_update_document', which might also involve creating or modifying content, so it misses full 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. It doesn't mention prerequisites, such as needing a Readwise account or API key, or compare it to siblings like 'readwise_save_document' for document-based operations. This lack of context leaves the agent without clear usage instructions.

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