Retrieves paginated metadata for either active or archived ChatGPT conversations, excluding message content, to help you browse and select sessions for organization.
分页读取网页会话元数据；不读取正文。只列普通或归档会话中的一种。
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| archived | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the description is free to add the traits that matter: results are paginated, only metadata is returned, and archived and normal conversations cannot be mixed. It stops short of noting auth requirements or page-size behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short clauses with no filler, and the key constraint (metadata only, not body) is front-loaded. Slightly telegraphic phrasing costs it polish but nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the agent would benefit from knowing what metadata fields come back and how paging is terminated, neither of which is stated. The essentials for calling correctly (read-only, paginated, archived toggle) are present, so it is adequate rather than complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry the parameter burden. It partially compensates by signaling pagination (limit/offset) and the exclusive archived/normal mode, but it never explains the defaults, the 1-100 limit cap, or the meaning of offset.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: paginated read of web conversation metadata, explicitly not the body. This distinguishes it from get_conversation/search_conversations without naming them, so it is clear but lacks explicit sibling routing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage through the constraint that only one of regular or archived conversations is listed, which maps to the archived flag. However, it never says when to use this versus chatgpt_search_conversations or chatgpt_list_project_conversations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.