Limitless MCP Server

limitless_get_lifelog_by_id

Retrieve a specific lifelog recording from the Limitless Pendant wearable by its unique ID to access personal audio data and transcriptions for AI analysis.

Instructions

Retrieves a single lifelog or Pendant recording by its specific ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lifelog_id": "<lifelog_id>"
    },
    "name": "limitless_get_lifelog_by_id"
  }
}

Input Schema

Name	Required	Description
`lifelog_id`	Yes	The unique identifier of the lifelog to retrieve.
`includeMarkdown`	No	Include markdown content in the response.
`includeHeadings`	No	Include headings content in the response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Retrieves' implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or what happens if the ID is invalid. For a tool with no annotations, this leaves significant gaps in understanding its 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 front-loaded with the core action, 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 no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., the structure of a lifelog, what 'markdown' or 'headings' content entails), leaving the agent uncertain about the response format. For a retrieval tool with rich 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%, so the schema fully documents the three parameters. The description adds no additional meaning beyond implying retrieval by ID, which is already covered in the schema. This meets the baseline of 3 where the schema does the heavy lifting.

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 ('Retrieves') and resource ('a single lifelog or Pendant recording'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'limitless_get_full_transcript' or 'limitless_get_detailed_analysis' that might also retrieve lifelog content but with different scopes or formats.

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 scenarios like needing a specific ID, nor does it reference sibling tools (e.g., 'limitless_list_lifelogs_by_date' for listing multiple lifelogs), leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server