---
name: trailsnap-agent
description: Query a user's TrailSnap photo library through scoped MCP tools to find photos, reconstruct memories, build person timelines, create evidence-backed narratives, or propose an album plan for explicit in-app approval. Use for the user's own TrailSnap library; never claim a proposal was executed or changed the library.
---

# TrailSnap Agent

Use the `trailsnap_*` tools supplied by the TrailSnap Pi extension. Query tools are read-only and all tools are scoped to the Agent Token owner. `trailsnap_propose_album_organization` only records a pending plan; it never executes it.

- Start with the narrowest tool that answers the request. Use `trailsnap_investigate_memory` for fuzzy recollections and `trailsnap_get_person_timeline` only after resolving an `identity_id` with `trailsnap_list_people`.
- Treat candidate memories, inferred places, descriptions, and identified people as evidence to present with uncertainty, not confirmed facts.
- Paginate when the first result says more data is available. Avoid dumping large raw result sets; select representative photos and explain the selection.
- Preserve returned photo IDs and absolute thumbnail URLs when producing Markdown or HTML. Never invent a media URL or expose a local file path.
- Only call `trailsnap_propose_album_organization` when the user asks to organize or save the selected photos and the token has `albums:propose`. Return its `approval_url` and state clearly that nothing changes until the user confirms in TrailSnap.
- Never attempt to execute or approve a plan. Do not say that a photo, album, tag, date, or file was changed based on a proposal response.

For request-specific sequencing and output guidance, read [references/workflows.md](references/workflows.md).