Skip to main content
Glama

browser_sessions

List all current browser sessions with their active state, current URL, creation time, last-used time, and trace status.

Instructions

List all current browser sessions with their active state, current URL, creation time, last-used time, and trace status.

中文详情:

  • 用途:列出当前所有浏览器会话,显示活跃状态、URL、创建时间、最后使用时间和 trace 录制状态

  • 何时使用:多会话测试前查看会话清单时;确认会话是否仍活跃时;排查 trace 录制状态时;调试并发会话问题时

  • 输出:{ ok: boolean, sessions: array, total: number } — 每项含 { name, active, url, createdAt, lastUsedAt, traceEnabled }

  • 参数:无

  • 错误:无活跃会话时返回空数组但 ok=true

  • 示例:{}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description details output structure and error behavior (empty array on no active sessions). It implicitly indicates a read operation, but does not discuss potential side effects, permissions, or rate limits. Annotations are absent, so the description carries the burden, which it mostly satisfies.

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?

Structured with English summary followed by Chinese details in bullet points. Generally concise, though some repetition between languages. Front-loaded with key information.

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 no output schema, the description compensates by specifying the return structure and error condition. Complete for a parameter-less listing tool, covering purpose, usage, output, and error handling.

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?

No parameters exist (schema coverage 100%). The description explicitly states '参数:无' (no parameters), confirming the absence of input. This meets the baseline for zero-parameter tools.

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 clearly states the tool lists all current browser sessions with specific details. It is distinct from siblings like browser_session_create or browser_session_close by being a list operation.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use scenarios in Chinese, such as before multi-session testing, checking activity, troubleshooting trace status, and debugging concurrent sessions. Also includes output and error case information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/validpilot/ai-verify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server