Skip to main content
Glama

Log the browser tab in

login

Signs a browser tab into the app under test using locally stored credentials, keeping passwords out of the model; handles sign-in forms or expired sessions and returns a run_in_page script if needed.

Instructions

Logs the browser tab under test into its app with a locally stored profile, without revealing the credentials. Call it whenever the app shows a login form or the session expired. With Chrome remote debugging it fills the tab itself; otherwise it returns run_in_page with a one-time script for you to run in the tab.

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": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoCurrent URL of the tab to log in. Recommended; required when several profiles or tabs exist.
profileNoProfile name from list_profiles. Needed only when several profiles match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it uses a locally stored profile without revealing credentials, and it explains the two execution paths. With Chrome remote debugging it fills the tab directly; otherwise it returns a run_in_page script for the agent to run, which is critical 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 three tight sentences, front-loads the core action, then gives usage guidance, then explains execution behavior. Every sentence carries useful information with no filler.

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?

For a two-parameter login tool with no output schema and informative annotations, the description covers what the tool does, when to call it, how it works with remote debugging, and what happens in the fallback path. Nothing an agent needs in order to invoke it correctly appears to be missing.

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 url and profile thoroughly. The description adds only indirect context through phrases like 'locally stored profile' and 'browser tab under test', without clarifying parameter usage beyond what the schema provides.

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 states a specific verb and resource: it logs the browser tab under test into its app using a stored profile. This clearly differentiates the action from status-checking siblings like login_status, though it does not explicitly name or compare against those 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?

It gives clear triggering conditions: call it when the app shows a login form or the session expired. It does not state when not to use it or explicitly name alternative tools, so guidance is strong but not exhaustive.

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