agent-prompt-capture

Overview Schema Source Related Servers Discussions Admin

list_sessions

List captured agent and browser chat sessions, newest first, with project, timestamps, and prompt counts. Use the returned session ID to read a full conversation.

Instructions

List agent/conversation sessions, most recently active first, with their project, first/last timestamp and prompt count. Use a returned session_id with list_prompts to read one conversation in order. source must be one of: claude_code, codex_cli, opencode, claude_web, claude_code_web, chatgpt_web, codex_cloud. limit is capped at 500.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`source`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses ordering, returned fields, source value restrictions, and the limit cap. It does not mention pagination or error behavior, but the stated behaviors are sufficient for a simple read-only list operation.

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?

Three dense sentences, with the primary purpose front-loaded and every sentence adding necessary detail. There is no filler or redundancy.

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 simplicity, optional parameters, and presence of an output schema, the description covers the essential operational details: ordering, returned fields, source constraints, limit cap, and integration with list_prompts. Nothing critical is missing for correct invocation.

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 description coverage is 0%, so the description must compensate for both parameters. It does: it enumerates valid source values and caps limit at 500. It does not mention defaults, but those are visible in the schema, so the added semantics are meaningful.

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?

The description states a specific verb and resource ('List agent/conversation sessions'), includes explicit ordering and output fields, and distinguishes itself from list_prompts by describing the follow-up role of the returned session_id. This makes it unambiguous what the tool returns and how it relates to sibling tools.

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

Usage Guidelines4/5

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

It gives clear context for use by stating the sort order, the fields returned, and the intended chaining with list_prompts via session_id. It does not explicitly contrast with siblings like activity_timeline or time_summary, but the companion usage is concrete and actionable.

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

Deploy Server