Browserbase MCP Server

Overview Schema Related Servers Score Discussions

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation3/5
The tools are organized into two clear sets: single-session and multi-session workflows, with act, extract, navigate, and observe tools duplicated for each. However, there is significant overlap between act/observe/extract in purpose, and the descriptions explicitly warn against misuse, indicating potential confusion. The screenshot tool also overlaps with extract for information gathering.
Naming Consistency4/5
Naming follows a consistent snake_case pattern with clear prefixes: 'browserbase_' for single-session and 'multi_browserbase_' for multi-session. The core action verbs (act, extract, navigate, observe) are reused consistently. Minor inconsistency exists with 'browserbase_session_close' vs. 'multi_browserbase_stagehand_session_close', but the pattern is mostly predictable.
Tool Count4/5
14 tools is reasonable for a browser automation server covering both single and parallel sessions. The duplication for multi-session workflows increases the count but serves a clear purpose. It might feel slightly heavy, but it aligns with the server's scope of providing comprehensive browser control capabilities.
Completeness5/5
The toolset provides complete coverage for browser automation: session creation, navigation, interaction (act/observe), data extraction, and session management (close/list). Both single and multi-session workflows are fully supported, with no obvious gaps in the lifecycle. The tools enable end-to-end automation tasks without dead ends.
Average 4.1/5 across 14 of 14 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under Apache 2.0.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that actions should be atomic and specific, and hints at behavioral traits like avoiding multi-step actions and using variables for sensitive data. However, it lacks details on error handling, performance implications, or what happens after the action (e.g., page changes).
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?
The description is appropriately sized and front-loaded with the core purpose. Every sentence adds value, such as examples and avoidance guidelines. However, it could be slightly more structured by separating usage tips from parameter guidance.
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?
Given the tool's complexity (web interaction with 3 parameters) and no annotations or output schema, the description is moderately complete. It covers purpose and usage but lacks details on behavioral outcomes, error cases, or integration with sibling tools, leaving gaps for an AI agent to infer.
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 parameters thoroughly. The description adds minimal value beyond the schema, as it repeats similar guidance about atomic actions but doesn't provide additional semantic context for parameters like sessionId or variables beyond what's in the schema.
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 clearly states the tool 'Performs an action on a web page element' with specific examples like 'Click the sign in button' or 'Type 'hello' into the search input'. It distinguishes from siblings by specifying it's for acting on web elements, unlike navigation or observation tools, but doesn't explicitly name alternatives.
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?
The description provides clear context for when to use this tool: for atomic, specific actions on web elements, with explicit examples of what to avoid (multi-step actions). It implies usage by suggesting 'use observe before using act' if unsure, but doesn't explicitly name when to choose this over other act-related siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the action ('navigate to a URL') but lacks details on permissions, rate limits, error handling, or what happens in the browser session. The guidance about URL reliability adds some context, but overall, it's insufficient for a mutation tool with zero annotation coverage.
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 concise and well-structured, consisting of two sentences that directly address the tool's purpose and usage guidelines. Every sentence adds value without redundancy, making it easy to understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (a navigation action in a browser session) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns, potential side effects, or how it interacts with other session tools. The usage guidance helps, but more behavioral context is needed for adequate completeness.
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%, with clear descriptions for both parameters ('sessionId' and 'url'). The description doesn't add any semantic details beyond what the schema provides, such as URL format requirements or session ID constraints. Given the high coverage, a baseline score of 3 is appropriate.
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 clearly states the tool's purpose: 'Navigate to a URL in the browser.' This is a specific verb ('navigate') with a resource ('URL'), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'browserbase_stagehand_navigate' (which lacks 'multi_' and 'session' in its name), though the context implies it's for multi-session scenarios.
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?
The description provides explicit usage guidance: 'Only use this tool with URLs you're confident will work and stay up to date. Otherwise, use https://google.com as the starting point (for a specific session).' This clearly states when to use it (with reliable URLs) and offers an alternative approach, though it doesn't name specific sibling alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions that URLs should be 'confident will work and stay up to date', which implies reliability concerns, but doesn't disclose other behavioral traits such as error handling, timeouts, or what happens if navigation fails. This leaves gaps in understanding the tool's behavior beyond the basic action.
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, front-loaded with the core action and followed by a usage guideline. Every sentence earns its place by providing essential information without waste, making it appropriately sized and well-structured.
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?
Given the tool's moderate complexity (navigation in a browser), no annotations, no output schema, and a simple input schema, the description is somewhat complete but has gaps. It covers the basic purpose and usage but lacks details on behavioral aspects like what happens after navigation, error conditions, or integration with other tools, making it adequate but not fully comprehensive.
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?
The input schema has 100% description coverage, with the 'url' parameter fully documented in the schema. The description doesn't add any additional meaning beyond what the schema provides, such as URL format requirements or examples. Baseline 3 is appropriate since the schema does the heavy lifting.
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 clearly states the verb 'navigate' and resource 'URL in the browser', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'multi_browserbase_stagehand_navigate_session', which appears to be a multi-session version, so it misses full sibling differentiation.
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?
The description provides clear context on when to use this tool ('with URLs you're confident will work and stay up to date') and suggests an alternative starting point ('use https://google.com as the starting point'), which helps guide usage. However, it doesn't explicitly mention when not to use it or compare it to other sibling tools like 'browserbase_stagehand_observe' or 'browserbase_stagehand_act', so it lacks full alternative naming.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It describes key behaviors: it performs a shutdown operation ('properly shutting down'), cleans up resources ('browser cleanup'), and terminates recordings ('terminates the session recording'). However, it lacks details on potential side effects (e.g., data loss, error handling) or prerequisites (e.g., must have an active session), which are important for a destructive 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?
The description is a single, well-structured sentence that efficiently conveys the action, mechanism, and outcomes without redundancy. It is front-loaded with the main purpose ('Closes the current Browserbase session') and adds necessary context in a logical flow, making it easy to parse and understand quickly.
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?
Given the tool's complexity (a session-closing operation with potential side effects), no annotations, and no output schema, the description is moderately complete. It covers what the tool does and its immediate effects but lacks information on return values, error conditions, or dependencies (e.g., must be called after session creation). For a tool that likely mutates state, more behavioral context would be beneficial.
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?
The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's action and effects. This meets the baseline for tools with no parameters, as it avoids unnecessary details.
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 specific action ('Closes') and resource ('current Browserbase session'), distinguishing it from siblings like browserbase_session_create (creates) and browserbase_screenshot (captures). It specifies the mechanism ('properly shutting down the Stagehand instance') and outcomes ('browser cleanup', 'terminates the session recording'), making the purpose unambiguous.
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?
The description implies usage context by mentioning 'current Browserbase session' and 'Stagehand instance', suggesting it should be used after session activities. However, it does not explicitly state when to use it versus alternatives (e.g., when to close vs. keep a session open) or name specific sibling tools for comparison, leaving some guidance implicit rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions that extraction 'works best when you provide clear, specific instructions' and 'a well-defined JSON schema for the expected output format,' which adds useful context about performance dependencies. However, it doesn't disclose potential limitations like rate limits, authentication needs, or error conditions, leaving some behavioral gaps.
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?
The description is appropriately sized (4 sentences) and front-loaded with the core purpose. Each sentence adds value: purpose, ideal use cases, when-to-use guidance, and performance advice. It could be slightly more concise by combining some advice, but overall it's efficient with minimal waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (extraction from web pages) and lack of annotations/output schema, the description does a good job covering purpose, usage guidelines, and performance context. It doesn't explain return values or error handling, which is a minor gap, but overall it provides sufficient context for an agent to use the tool effectively.
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 fully documents the single 'instruction' parameter. The description adds marginal value by emphasizing that instructions should be 'clear, specific' and providing examples, but doesn't introduce new semantic information beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.
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's purpose: 'Extracts structured information and text content from the current web page based on specific instructions and a defined schema.' It specifies the verb (extracts), resource (current web page), and distinguishes from sibling tools like 'observe' for interactive elements.
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?
The description provides explicit guidance: 'Use this tool when you need to get text content, data, or information from a page rather than interacting with elements. For interactive elements like buttons, forms, or clickable items, use the observe tool instead.' It clearly defines when to use this tool versus alternatives, including a specific sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that extraction works best with clear instructions and a well-defined schema, adding useful context about performance and prerequisites. However, it lacks details on error handling, rate limits, or authentication needs, leaving gaps in behavioral transparency for a tool with no annotation support.
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?
The description is appropriately sized and front-loaded, with the core purpose stated first. Every sentence adds value, such as usage guidelines and performance tips, but it could be slightly more concise by avoiding minor redundancy (e.g., repeating 'specific' and 'extract'). Overall, it's efficient with zero waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (extraction with instructions and schema) and lack of annotations or output schema, the description does well by covering purpose, usage, and behavioral tips. However, it could improve by mentioning output format or error cases, as there's no output schema to rely on. It's mostly complete but has minor gaps.
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 both parameters thoroughly. The description adds minimal value beyond the schema by emphasizing the importance of specific instructions, but it doesn't provide additional syntax or format details. This meets the baseline of 3 when schema coverage is high.
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's purpose with specific verbs ('extracts structured information and text content') and resources ('from the current web page'), distinguishing it from sibling tools like 'observe' for interactive elements. It explicitly mentions extraction based on instructions and schema, making the function unambiguous.
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?
The description provides explicit guidance on when to use this tool ('when you need to get text content, data, or information from a page') and when not to ('for interactive elements like buttons, forms, or clickable items, use the observe tool instead'). It also offers alternatives by naming the 'observe' tool, ensuring clear differentiation from siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by describing the session's isolated nature ('independent cookies, authentication, and state') and its purpose for scaling automation. However, it lacks details on error handling, performance implications, or resource constraints that would be helpful for a creation tool.
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?
The description is well-structured and front-loaded with the core purpose. Most sentences add value, such as use cases and pairing guidance, though it could be slightly more concise by combining some of the listed examples into a broader category.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (creating parallel sessions) and lack of annotations/output schema, the description does a good job explaining the tool's role and usage. It covers the 'why' and 'how' effectively, though it could benefit from mentioning potential limitations or prerequisites for multi-session workflows.
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 fully documents both parameters. The description adds no additional parameter semantics beyond what's in the schema, but it doesn't need to since the schema is comprehensive. Baseline 3 is appropriate when the schema does the heavy lifting.
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's purpose: 'Create parallel browser session for multi-session workflows.' It specifies the verb ('create'), resource ('parallel browser session'), and distinguishes from siblings by emphasizing multi-session capabilities, unlike the single-session 'browserbase_session_create'.
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?
The description provides explicit guidance on when to use this tool: 'Use this when you need multiple browser instances running simultaneously' and lists specific use cases (parallel data scraping, concurrent automation, etc.). It also states when to pair with other tools: 'Always pair with session-specific tools (those ending with '_session').'
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It describes the tool's behavioral traits well: it performs actions on web elements, emphasizes atomicity, and advises using 'observe' first. However, it lacks details on error handling, performance characteristics, or what happens if the element isn't found, leaving some behavioral aspects unclear.
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 concise and well-structured: it states the purpose in the first sentence, provides usage guidelines with clear examples and anti-examples, and avoids redundancy. Every sentence adds value without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (interactive web actions) and lack of annotations or output schema, the description is mostly complete. It covers purpose, usage, and behavioral traits effectively. However, it could improve by mentioning potential side effects or dependencies on prior steps like navigation, but it's sufficient for an agent to use the tool correctly.
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 fully documents both parameters. The description adds minimal value beyond the schema, as it repeats the same examples and guidelines for the 'action' parameter. It doesn't provide additional context or semantics not already covered in the schema descriptions.
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's purpose: 'Performs an action on a web page element.' It specifies the verb ('performs an action') and resource ('web page element'), and distinguishes it from siblings like 'observe' or 'navigate' by focusing on interactive actions rather than observation or navigation.
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?
The description provides explicit guidance on when to use this tool: for atomic, specific actions like clicking buttons or typing text. It explicitly advises against multi-step actions and suggests using 'observe' before 'act' if unsure, clearly differentiating it from alternatives like 'navigate' or 'extract'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it returns detailed information about identified elements (properties, location, interaction capabilities), explains that results are used to craft precise actions, and notes that specificity improves accuracy. However, it doesn't mention potential limitations like timeouts, error conditions, or what happens if no elements are found.
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?
The description is appropriately sized and front-loaded with the core purpose in the first sentence. Most sentences add value, though some repetition occurs (e.g., emphasizing specificity multiple times). It could be slightly more concise by combining related points about element identification and usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (identifying interactive elements), no annotations, and no output schema, the description does a good job explaining what the tool does, when to use it, and what it returns. It covers the essential context for an agent to understand the tool's role in a workflow. However, without an output schema, more detail about the return format would be helpful.
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 both parameters thoroughly. The description adds some context by emphasizing the importance of specific instructions and linking to the 'act' tool, but doesn't provide additional semantic meaning beyond what's in the schema descriptions. This meets the baseline for high schema coverage.
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's purpose with specific verbs ('observes and identifies') and resources ('interactive elements on the current web page'), and explicitly distinguishes it from sibling tools like 'extract' for text content and 'act' for performing actions. It provides a comprehensive list of target elements (buttons, links, form fields, etc.) that goes beyond a generic statement.
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?
The description explicitly states when to use this tool ('when you need to locate elements before performing actions with the act tool') and when not to use it ('DO NOT use this tool for extracting text content or data - use the extract tool instead'). It clearly differentiates from alternatives like 'extract' and 'act', providing strong guidance on tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses key behavioral traits: the tool returns 'detailed information about the identified elements including their properties, location, and interaction capabilities,' explains that 'the more specific your observation instruction, the more accurate the element identification will be,' and clarifies this is for 'a specific session.' However, it doesn't mention potential limitations like timeouts, error conditions, or performance characteristics.
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?
The description is appropriately sized and front-loaded with core purpose. Most sentences earn their place by providing usage guidance, behavioral context, or practical advice. However, some phrasing could be more concise (e.g., 'Think of this as your 'eyes' on the page' is somewhat redundant with earlier explanation).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 3 parameters, no annotations, and no output schema, the description does well to explain the tool's purpose, usage context, and behavioral characteristics. It covers what the tool does, when to use it, and what information it returns. The main gap is lack of output format details (though mentioned generally), but for a tool with good parameter documentation and clear purpose, this is reasonably complete.
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 three parameters thoroughly. The description adds some context about the 'instruction' parameter ('The more specific your observation instruction, the more accurate the element identification will be'), but doesn't provide additional meaning beyond what's in the schema descriptions. Baseline 3 is appropriate when schema does the heavy lifting.
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's purpose: 'Observes and identifies specific interactive elements on the current web page that can be used for subsequent actions.' It specifies the verb (observe/identify), resource (interactive elements), and scope (current web page). It distinguishes from siblings by explicitly contrasting with 'extract' for text content and positioning as preparatory for 'act' tool usage.
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?
The description provides explicit usage guidance: 'Use this tool when you need to locate elements before performing actions with the act tool. DO NOT use this tool for extracting text content or data - use the extract tool instead for that purpose.' It names specific alternatives (act, extract) and provides clear when-to-use and when-not-to-use criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the tool's purpose (visual feedback for browser control) but doesn't address important behavioral aspects like whether it captures the full page or viewport, image format, storage location, or performance implications. It provides some context but leaves significant gaps.
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 perfectly concise with three sentences that each serve distinct purposes: stating the action, explaining the primary use case, and providing usage constraints. There is zero wasted text, and the information is front-loaded with the core functionality.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema and no annotations, the description does a good job explaining the tool's purpose and usage context. However, it doesn't address what the tool returns (image data, file path, etc.) or potential limitations, which would be helpful given the lack of structured output documentation.
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?
With 100% schema description coverage for the single parameter, the baseline would be 3. However, the description adds value by implicitly explaining why you might want to name screenshots (to track your position during browser control sessions), providing semantic context beyond the schema's technical documentation of the 'name' parameter.
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 specific action ('Takes a screenshot') and resource ('of the current page'), distinguishing it from sibling tools like navigation or extraction tools. It provides a concrete verb+resource combination that leaves no ambiguity about what the tool does.
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?
The description provides explicit guidance on when to use this tool ('to learn where you are on the page when controlling the browser with Stagehand') and when not to use it ('Only use this tool when the other tools are not sufficient to get the information you need'). This clearly distinguishes it from alternative information-gathering tools in the sibling set.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it can create or reuse sessions, initializes Stagehand with the session, updates the active session, and supports various configuration flags (proxies, stealth, viewport, cookies). The WARNING about single-session limitation is particularly valuable. It doesn't cover rate limits or detailed error handling, but provides substantial operational context.
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 efficiently structured with zero wasted sentences. It front-loads the core purpose, immediately provides the critical warning about single-session limitation with explicit alternative, then adds important behavioral details. Every sentence earns its place by providing essential information for tool selection and usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (session management with Stagehand initialization) and no annotations or output schema, the description does an excellent job covering operational context. It explains what the tool does, when to use it, key behavioral characteristics, and distinguishes it from alternatives. The main gap is lack of information about return values or error conditions, but overall it provides substantial context for effective tool usage.
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% (the single parameter 'sessionId' is fully documented in the schema). The description doesn't add any parameter-specific information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no additional parameter information in the description.
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 specific action ('Create or reuse a single cloud browser session') and resource ('Browserbase with fully initialized Stagehand'). It explicitly distinguishes this tool from its sibling 'multi_browserbase_stagehand_session_create' by emphasizing it's for SINGLE browser workflows only, providing clear differentiation.
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?
The description provides explicit guidance on when to use this tool ('for SINGLE browser workflows only') and when not to use it ('If you need multiple browser sessions running simultaneously... use 'multi_browserbase_stagehand_session_create' instead'). It clearly names the alternative tool and specifies the appropriate context for each.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it lists active sessions with specific attributes (IDs, names, ages, Browserbase session IDs) and is critical for debugging and resource management. However, it lacks details on potential limitations like rate limits, error handling, or whether it requires authentication, which could be important for an agent's decision-making.
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?
The description is front-loaded with key information ('ONLY WORKS WITH MULTI-SESSION TOOLS!') and uses concise sentences to explain purpose and usage. However, it includes some repetitive emphasis (e.g., 'Critical tool', 'Essential for debugging') that slightly reduces efficiency, though overall it remains well-structured and informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (multi-session management), no annotations, no output schema, and 0 parameters, the description is largely complete. It explains what the tool does, when to use it, and its importance in workflows. However, it could benefit from mentioning the output format or any dependencies, but for a parameter-less tool, this is a minor gap.
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?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not discuss parameters, which is appropriate. A baseline score of 4 is applied since the tool has no parameters, and the description focuses on usage context without redundancy.
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's purpose: 'Track all parallel sessions' and 'Shows all active browser sessions with their IDs, names, ages, and Browserbase session IDs.' It specifies the verb ('track', 'shows') and resource ('parallel sessions', 'active browser sessions'), and distinguishes itself from sibling tools by emphasizing its role in multi-session management, unlike session-specific tools like browserbase_session_create or browserbase_stagehand_act.
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?
The description provides explicit guidance on when to use this tool: 'ONLY WORKS WITH MULTI-SESSION TOOLS!' and 'Use this frequently to monitor your parallel automation workflows, verify sessions are running, and get session IDs for session-specific tools.' It also mentions alternatives implicitly by referencing 'session-specific tools' for further actions, making it clear this is for monitoring and management rather than direct session operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a destructive operation ('once closed, the session cannot be recovered'), has financial implications ('billing charges'), and resource management consequences ('frees cloud resources', 'each unclosed session continues consuming resources'). It doesn't mention error handling or response format.
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 efficiently structured with three sentences that each earn their place: first states purpose, second gives usage guidelines, third emphasizes importance. No wasted words, and key information is front-loaded about cleanup and termination.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive tool with no annotations and no output schema, the description provides strong context about the operation's consequences and importance. It covers the critical 'why' and 'when' aspects well, though doesn't describe what happens on success/failure or return values.
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 100%, so the baseline is 3. The description adds value by emphasizing the criticality of the sessionId parameter ('Double-check this ID') and providing context about where to get it ('from multi_browserbase_stagehand_session_list'), which goes beyond the schema's technical documentation.
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 specific action ('cleanup', 'properly terminates', 'ends', 'frees') and resource ('parallel session for multi-session workflows', 'browser session', 'Browserbase session', 'cloud resources'). It distinguishes from sibling tools like 'browserbase_session_close' by specifying it's for 'multi-session workflows' and 'parallel sessions'.
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?
The description provides explicit guidance on when to use ('Always use this when finished with a session') and why ('to avoid resource waste and billing charges', 'Critical for responsible multi-session automation'). It distinguishes from alternatives by specifying it's for 'parallel session' cleanup in multi-session contexts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![mcp-server-browserbase MCP server](https://glama.ai/mcp/servers/Xxx00xxX33/mcp-server-browserbase/badges/card.svg)](https://glama.ai/mcp/servers/Xxx00xxX33/mcp-server-browserbase)

Score Badge

Copy to your README.md:

[![mcp-server-browserbase MCP server](https://glama.ai/mcp/servers/Xxx00xxX33/mcp-server-browserbase/badges/score.svg)](https://glama.ai/mcp/servers/Xxx00xxX33/mcp-server-browserbase)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/Xxx00xxX33/mcp-server-browserbase'

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