Skip to main content
Glama
S2thend

cursor-history-mcp

by S2thend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cursor_history_list

List Cursor AI chat sessions with metadata like workspace, message count, and timestamps. Filter by workspace, set limits, and paginate to find specific sessions for review or export.

Instructions

List Cursor AI chat sessions. Returns recent sessions with metadata including workspace, message count, and timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of sessions to return (default: 20, max: 1000)
offsetNoNumber of sessions to skip for pagination (default: 0)
workspaceNoWorkspace path. Reuse the same scope for listing and reading a session index.
includeCrossWorkspaceSourcesNoOpt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / includeCrossWorkspaceSources
      Added value: +{
+  "default": false,
+  "description": "Opt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / workspace / description
      Previous value: -"Filter sessions by workspace path (absolute path to project folder)"New value: +"Workspace path. Reuse the same scope for listing and reading a session index."
  2. First observedv0.2.4

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool returns recent sessions with workspace, message count, and timestamps, but it doesn't specify ordering guarantees, pagination behavior, or whether session IDs are included in the results.

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?

The description is two sentences with no filler. The primary action is front-loaded and the return metadata is stated immediately, making it easy to scan.

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

Completeness3/5

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

The description adequately summarizes the return payload but, with no output schema, it should clarify whether session IDs are returned so an agent can feed them into sibling tools like cursor_history_show. Sorting semantics and scope behavior are also left implicit.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all four parameters. The description adds no parameter-specific meaning beyond what the schema provides, which matches the baseline for fully covered schemas.

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

Purpose4/5

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

The description uses a specific verb and resource ('List Cursor AI chat sessions') and names the return content. It doesn't explicitly distinguish itself from the sibling cursor_history_search, but the list vs. search contrast is reasonably inferable.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool instead of cursor_history_search, cursor_history_show, or other siblings. The phrase 'recent sessions' implies a browsing use case, but there are no explicit when-to-use or when-not-to-use conditions.

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

Deploy Server

Other Tools