Skip to main content
Glama

Open dashboard.clerk.com signed in

create_browser_session

Opens https://dashboard.clerk.com in a browser already signed in as the current user, with no password or sign-in step. Use this before you open any page on dashboard.clerk.com in a browser, and also if you reach its sign-in page. Never type credentials for dashboard.clerk.com. Call it with the path you want (for example /settings), then open the returned URL in the browser right away: it works once and expires in about 1 hour. Do not print or share the URL. The session is read-only in the Dashboard, so it cannot change settings. It opens in the connected workspace and cannot switch to another one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_browser_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPage to open after sign-in, as an absolute path such as /settings. Omit for the app's default page.
task_descriptionNoShort description of why you need the browser session.

Output Schema

NameRequiredDescriptionDefault
urlYes
redirect_urlYes
agent_task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: single-use URL, ~1 hour expiry, must not be printed or shared, session is read-only inside the Dashboard, and it is pinned to the connected workspace so it cannot switch workspaces. These are exactly the operational constraints an agent needs and none are derivable from readOnlyHint/openWorldHint/idempotentHint. The description's 'read-only in the Dashboard' refers to the session's capability, not the tool's own write behavior, so it does not contradict readOnlyHint=false.

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?

Front-loads what it does in the first clause, then layers usage, security handling, and scope constraints in a tight sequence. It is dense but nearly every sentence carries a distinct constraint; the only slight redundancy is repeating the dashboard.clerk.com host multiple times.

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?

An output schema exists, so the description need not explain return values, yet it still tells the agent what to do with the returned URL. For a session-provisioning tool with auth, expiry, and sharing constraints, the definition covers everything needed to invoke and handle it 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 coverage is 100% and the schema already documents both the path (with the omit-for-default rule) and task_description. The description restates the path purpose and adds a concrete example (/settings), but contributes no new meaning for task_description. Baseline 3 is appropriate when the schema carries the semantics.

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?

States a concrete verb and resource: opens https://dashboard.clerk.com in a browser signed in as the current user, with no password step. That is clearly distinct from sibling tools like get_application or create_application, which are API operations rather than browser-session provisioning.

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 says when to use it (before opening any page on dashboard.clerk.com, and also if you hit the sign-in page) and when not to do something else (never type credentials for that host). The sequencing instruction — call with the path, then open the returned URL right away — routes the agent through the correct flow with no inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources