get-snapshot

Retrieve full snapshot details including content, enrichment, and metadata by ID.

Overview

The get-snapshot tool retrieves complete snapshot information by ID. Unlike list-snapshots which returns metadata summaries, this tool returns the full conversation content along with all enrichment data.

What You Get

•Full conversation content (can be large)
•AI-generated summary and category
•Extracted key points and concepts
•Action items and next steps
•All 13 categories of metadata (if provided)
•Privacy scope and timestamps

When to Use

Use this tool when you need to:

• Read the full content of a specific snapshot
• Access complete metadata for analytics
• Display snapshot details in a UI
• Verify snapshot contents before deletion
• Export or back up specific conversations
• Build on previous work by retrieving full context

Parameters

snapshotIdREQUIRED

Type: string

The UUID of the snapshot to retrieve.

Example: "550e8400-e29b-41d4-a716-446655440000"

includeMetadataOPTIONAL

Type: boolean

Whether to include all 13 metadata categories in the response. Set to false to reduce response size if you only need the content.

Default: true

Response

Returns complete snapshot details:

{
  "success": true,
  "snapshot": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "workspaceId": "workspace-abc-123",
    "content": "Full conversation content here. This can be quite long,
containing the entire discussion, code snippets, decisions made,
and context from the original snapshot.",

    "summary": "Discussed OAuth 2.0 implementation using Supabase Auth
with GitHub and Google providers. Decided on implementation approach
and timeline.",

    "category": "implementation",
    "scope": "workspace",

    "keyPoints": [
      "OAuth 2.0 chosen for authentication",
      "Supabase Auth provides simplicity and good developer experience",
      "GitHub and Google providers will be configured",
      "Implementation scheduled for next sprint"
    ],

    "concepts": [
      "authentication",
      "oauth 2.0",
      "supabase",
      "github provider",
      "google provider"
    ],

    "actionItems": [
      "Set up GitHub OAuth provider in Supabase dashboard",
      "Configure Google OAuth credentials",
      "Implement auth flow in frontend",
      "Add error handling for auth failures"
    ],

    "createdAt": "2025-10-15T14:30:00Z",
    "updatedAt": "2025-10-15T14:30:00Z",

    "metadata": {
      "client": {
        "name": "Claude Desktop",
        "version": "0.7.2",
        "platform": "darwin"
      },
      "session": {
        "id": "session-abc123",
        "device": {
          "type": "desktop",
          "os": "macOS 14.0"
        }
      },
      "conversation": {
        "threadId": "thread-xyz789",
        "messageCount": 23,
        "durationMs": 1847000,
        "model": "claude-3-5-sonnet"
      },
      "workspace": {
        "name": "my-saas-app",
        "path": "/Users/dev/my-project",
        "git": {
          "branch": "feature/auth",
          "commit": "a3f4b2c"
        }
      },
      "content": {
        "language": "en",
        "codeLanguages": ["typescript", "tsx"],
        "topics": ["authentication", "oauth"]
      }
      // ... up to 13 metadata categories
    }
  }
}

Note: The content field can be very large (thousands of lines). Be mindful of token usage when retrieving multiple snapshots.

Error Responses

Snapshot Not Found

{
  "success": false,
  "error": "Snapshot not found",
  "code": "NOT_FOUND"
}

Access Denied

{
  "success": false,
  "error": "You do not have permission to access this snapshot",
  "code": "FORBIDDEN"
}

This occurs when trying to access a private snapshot that belongs to another user, or a workspace snapshot you don't have access to.

Examples

Basic Usage

get-snapshot({
  snapshotId: "550e8400-e29b-41d4-a716-446655440000"
})

Without Metadata

get-snapshot({
  snapshotId: "550e8400-e29b-41d4-a716-446655440000",
  includeMetadata: false
})

Reduces response size by excluding the 13 metadata categories. Only returns core fields like content, summary, keyPoints, etc.

Typical Workflow

// 1. Search for relevant snapshots
const results = query-workspace({
  query: "authentication implementation"
})

// 2. Get the full content of the most relevant one
const snapshot = get-snapshot({
  snapshotId: results.results[0].snapshotId
})

// 3. Use the full content to inform your work
console.log(snapshot.content)
console.log(snapshot.actionItems)

Best Practices

✓Get IDs from search first: Use query-workspace or list-snapshots to find the right snapshot ID
✓Be mindful of token usage: Large snapshots can consume significant tokens - only retrieve when needed
✓Use includeMetadata wisely: Set to false if you only need the conversation content
✓Handle errors gracefully: Check for NOT_FOUND and FORBIDDEN error codes
✓Cache when appropriate: If building a UI, cache retrieved snapshots to avoid redundant requests