Skip to main content
Glama
199-mcp

Limitless MCP Server

by 199-mcp

limitless_get_lifelog_by_id

Retrieve a specific lifelog or Pendant recording by its unique ID to access detailed conversation content and analytics.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lifelog_idYesThe unique identifier of the lifelog to retrieve.
includeMarkdownNoInclude markdown content in the response.
includeHeadingsNoInclude headings content in the response.

Implementation Reference

  • src/server.ts:438-442 (registration)
    MCP tool registration for 'limitless_get_lifelog_by_id', which wraps the getLifelogById function call.
    server.tool( "limitless_get_lifelog_by_id",
        "Retrieves a single lifelog or Pendant recording by its specific ID.",
        GetByIdArgsSchema,
        async (args, _extra) => handleToolApiCall(() => getLifelogById(limitlessApiKey, args.lifelog_id, { includeMarkdown: args.includeMarkdown, includeHeadings: args.includeHeadings }))
    );
  • The core handler function that makes the API request to retrieve a single lifelog by its ID from the Limitless API.
    export async function getLifelogById(apiKey: string, lifelogId: string, options: Pick<LifelogParams, 'includeMarkdown' | 'includeHeadings'> = {}): Promise<Lifelog> {
        // Cannot log here reliably for stdio
        // console.error(`[Limitless Client] Requesting lifelog by ID: ${lifelogId}`);
        const params: Record<string, string | number | boolean | undefined> = {
            includeMarkdown: options.includeMarkdown ?? true,
            includeHeadings: options.includeHeadings ?? true,
        };
        const response = await makeApiRequest<SingleLifelogResponse>(apiKey, `v1/lifelogs/${lifelogId}`, params);
        if (!response.data?.lifelog) {
            throw new LimitlessApiError(`Lifelog with ID ${lifelogId} not found`, 404);
        }
        return response.data.lifelog;
    }
  • Zod schema defining the input arguments for the tool, including the required lifelog_id.
    const GetByIdArgsSchema = {
        lifelog_id: z.string().describe("The unique identifier of the lifelog to retrieve."),
        includeMarkdown: z.boolean().optional().default(true).describe("Include markdown content in the response."),
        includeHeadings: z.boolean().optional().default(true).describe("Include headings content in the response."),
    };
  • TypeScript interface defining the structure of a Lifelog object returned by the API.
    export interface Lifelog {
        id: string;
        title?: string;
        markdown?: string;
        startTime: string;
        endTime: string;
        contents?: LifelogContentNode[]; // Use specific type
        isStarred?: boolean; // Whether this lifelog is starred
        updatedAt?: string; // When this lifelog was last updated
        // Add other fields from the API response as needed
    }
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.

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/199-mcp/mcp-limitless'

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