Skip to main content
Glama
TT-Wang

cortex

by TT-Wang
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

transcript_search

Search raw Claude Code session transcripts to retrieve past conversation excerpts and full context from prior sessions.

Instructions

Search raw Claude Code session transcripts for past conversation excerpts.

This is the DIFFERENT from memory_recall — it searches the raw session JSONL files under ~/.claude/projects/, not the mined memory corpus. Use it when you need to find the actual back-and-forth of a prior conversation, not the distilled lesson from it.

Behaviour:

  • Read-only. Does not modify transcripts, memories, or any index.

  • No authentication required.

  • No rate limits. Latency scales with transcript corpus size; typical 100-500ms across a year of daily sessions.

  • Data access scope: reads ~/.claude/projects/**/*.jsonl via direct filesystem access. Does NOT read ~/obsidian-brain/ (that's what memory_recall and memory_list are for). Nothing is sent over the network.

  • Idempotent and deterministic for a given filesystem state.

  • Failure modes: returns "No matching sessions" on empty result sets. Sessions older than Claude Code's 30-day retention window are not searchable (they've been deleted).

Use transcript_search when:

  • You want to recall "what did I actually say three weeks ago about X"

  • A mined memory references a session and you want the full context

  • You want to find all sessions that touched a specific file or topic

  • You're verifying a memory's source_session or debugging extraction

Do NOT use for:

  • Looking up durable knowledge (use memory_recall — mined, ranked, faster)

  • Listing memories (use memory_list)

  • Query-tailored context briefings (use context_assemble)

Returns: Markdown-formatted session excerpts with the session id, date, and matched text, or "No matching sessions" if nothing matches. Transcripts older than Claude Code's 30-day retention are not searchable.

Example: transcript_search(query="redis connection pool size", limit=3)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of session excerpts to return. Each excerpt is a short quote with the session id and date.
queryYesSearch phrase or keyword list. Matches against the raw Claude Code session JSONL transcripts (not the mined memory corpus). Use this for session-level context recovery, not durable knowledge lookup.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations provided, so description fully covers behavior: read-only, no auth required, no rate limits, data access scope (reads ~/.claude/projects/**), idempotent, failure modes, retention window. Highly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections, but somewhat lengthy. Could be slightly more concise without losing clarity, but overall effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and lack of annotations, description covers all necessary aspects: purpose, usage, behavior, parameters, return format, and failure modes. Output schema exists but description still adequately describes return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds useful context beyond schema: explains that query matches against raw session files, and limit controls number of excerpts returned. Provides example usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it searches raw Claude Code session transcripts for conversation excerpts. Distinguishes from sibling tool memory_recall by specifying it searches raw JSONL files, not the mined memory corpus.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists when to use (e.g., recalling past conversations, verifying memory sources) and when not to use (e.g., durable knowledge lookup, listing memories), with specific alternative tool names.

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/TT-Wang/memem'

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