Skip to main content
Glama

List Exploratory Sessions

list_sessions
Read-only

Browse a project's exploratory sessions and filter by status, state, type, assignee, release, tags, or name search to find relevant sessions quickly.

Instructions

Browse exploratory sessions for a project. Filter by status (active|closed), state, sessionType, assignee, release (releaseId), tags, or free-text search on name. Default page size 25 (max 200).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "list_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
tagsNoSingle tag or comma-separated tags
limitNoDefault 25
stateNoWorkflow state. Pass either the canonical form ("new", "under_review", "done", "rejected") or the display form ("Under review", "Done") — the server normalizes (lowercase, spaces → underscores) so UI badges colorize correctly.
searchNoMatch by session name
sortByNo
statusNo
isClosedNo
projectIdYesProject ID
releaseIdNoFilter to sessions in this release. Pass "none" for unlinked.
sortOrderNo
sessionTypeNo
assigneeUserIdNoUser _id (e.g. "user_abc...") OR email address — both are accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / assigneeUserId / description
      Previous value: -"User _id OR email — both accepted (server resolves email to user _id)."New value: +"User _id (e.g. \"user_abc...\") OR email address — both are accepted."
    • changedInput schema / properties / limit / description
      Previous value: -"Default 25 (max 200)."New value: +"Default 25"
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / releaseId / description
      Previous value: -"'none' for unlinked sessions."New value: +"Filter to sessions in this release. Pass \"none\" for unlinked."
    • changedInput schema / properties / search / description
      Previous value: -"Match by session name."New value: +"Match by session name"
    • changedInput schema / properties / state / description
      Previous value: -"Workflow state. Either canonical ('under_review', 'done') or display ('Under review', 'Done') form — the server normalizes lowercase+underscored."New value: +"Workflow state. Pass either the canonical form (\"new\", \"under_review\", \"done\", \"rejected\") or the display form (\"Under review\", \"Done\") — the server normalizes (lowercase, spaces → underscores) so UI badges colorize correctly."
    • changedInput schema / properties / tags / description
      Previous value: -"Single tag or comma-separated."New value: +"Single tag or comma-separated tags"
  2. Addedv1.0.10

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the pagination default and cap (25, max 200), which is mildly useful behavioral context, but it says nothing about return shape, total counts, or how status and isClosed interact. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the resource and scope, then the filterable dimensions, then pagination limits. No filler, though it could group the enumeration more tightly.

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?

For a 13-parameter read tool with no output schema, the description should ideally describe what a session record contains and how the two status-related parameters (status enum vs isClosed boolean) relate. It covers filtering and pagination adequately but leaves sorting, paging, and returned data unaddressed.

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?

With schema coverage at 54%, the description partially compensates by mapping human-readable filter names to parameters (assignee → assigneeUserId, release → releaseId) and clarifying that search is free-text on name. It omits meaning for page, sortBy/sortOrder, isClosed, and how state normalization works, leaving several of the 13 parameters to the schema alone.

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 gives a specific verb and resource ("Browse exploratory sessions for a project") that immediately identifies the operation. It does not, however, distinguish this tool from the many sibling list_* tools (list_manual_runs, list_testcase, etc.), so an agent gets no explicit differentiation cue.

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

Usage Guidelines3/5

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

Usage is implied by the enumeration of filters and the projectId requirement, which tells an agent this is the browse/search path for sessions. There is no explicit when-to-use vs when-not guidance, no mention of an alternative for fetching a single session (e.g. a get-session sibling), and no stated prerequisites or permissions.

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