Skip to main content
Glama

save_auth

Log into web applications and save authentication sessions to JSON for screen-reader analysis of protected content. Executes login steps, captures cookies and localStorage, enabling accessibility testing on authenticated pages.

Instructions

Authenticate with a web application and save the session for subsequent analysis. Navigates to the URL, executes login steps (click a button, fill a form, etc.), waits for the authenticated page to load, then saves cookies and localStorage to a JSON file. Overwrites the output file if it already exists.

Side effects: Writes a storageState JSON file to disk at outputPath. Launches a headed browser that interacts with the page (clicks, fills inputs). Not needed for public pages — only use when content is behind authentication.

Pass the output file path as storageState to analyze_url, trace_path, or analyze_pages to analyze authenticated content.

Steps format: Array of actions to perform in order. Each step is an object:

  • { click: 'button text or selector' } — click a button/link

  • { fill: ['input selector', 'value'] } — fill an input field

  • { wait: 2000 } — wait N milliseconds

  • { waitForUrl: '/dashboard' } — wait until URL contains this string

Example for a dev login: steps: [{ click: 'Dev Login' }, { waitForUrl: '/workspace' }] Example for form login: steps: [{ fill: ['#email', 'user@test.com'] }, { fill: ['#password', 'pass'] }, { click: 'Sign In' }, { waitForUrl: '/dashboard' }]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesLogin page URL
stepsYesLogin steps to execute (see description for format)
outputPathNoFile path to save the storageState JSONtactual-auth.json
timeoutNoTimeout per step in ms
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden effectively. It explicitly warns about file overwrites ('Overwrites the output file'), documents the headed browser launch, and details the interaction side effects (clicks, fills). Minor gap: doesn't describe failure modes if authentication steps fail.

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?

Lengthy but appropriately so given the complexity of the 'steps' DSL. Well-structured with bold headers ('Side effects', 'Steps format') that allow scanning. The main purpose is front-loaded in the first sentence, and every section serves a distinct function (behavioral warning, integration guide, syntax specification).

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?

Comprehensive for a tool lacking both annotations and output schema. Explains the output file's purpose (cookies/localStorage storage), format (JSON), and consumption pattern (pass to sibling tools). Could improve by describing error conditions or the structure of the saved storageState file.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description adds critical value for the complex 'steps' parameter, which lacks structural constraints in the schema (just 'array of objects'). It defines the specific action types (click, fill, wait, waitForUrl), their formats, and provides concrete JSON examples—essential information not present in the structured schema.

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 opens with specific verbs ('Authenticate... and save') and clearly identifies the resource (web application session). It explicitly distinguishes this tool from siblings by stating it's 'Not needed for public pages' and listing the specific sibling tools (analyze_url, trace_path, analyze_pages) that consume its output.

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?

Provides explicit when-to-use guidance ('only use when content is behind authentication') and clear integration instructions ('Pass the output file path as `storageState` to analyze_url, trace_path, or analyze_pages'). The side effects section further clarifies behavioral boundaries.

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/tactual-dev/tactual'

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