Skip to main content
Glama

auth_update_profile

Create or update an authentication profile for visual QA testing. Configure tokens, cookies, OAuth, or storage to access protected pages before capturing screenshots.

Instructions

Create or update an auth profile. Only the fields you pass change (dicts are merged).

Any secret may be given as "env:VAR_NAME" so it is read from the server's environment instead of passing through the conversation — prefer that.

origins: origins that receive headers/tokens, e.g. ["https://app.example.com"] (default: the base_url's origin). Credentials are never sent to other origins. access_token/token_type/expires_in/refresh_token: a bearer token you already have. apply_token_as: where the app expects the token — any of "header" (Authorization: Bearer), "header:X-Api-Key", "local_storage:", "session_storage:", "local_storage_json:" (whole token object as JSON), "cookie:". oauth: {grant_type: client_credentials|password|refresh_token|authorization_code, token_url, client_id, client_secret, scope, audience, username, password, authorize_url, redirect_uri, client_auth: post|basic, extra_params}. For client_credentials/password a token is fetched immediately and refreshed automatically. For authorization_code, call auth_oauth_login next. cookies: Playwright cookies [{name, value, url} or {name, value, domain, path}]. local_storage/session_storage: {origin: {key: value}} injected before page scripts run. http_credentials: {username, password} for HTTP basic auth. clear: field names to remove, e.g. ["token", "cookies", "storage_state"].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
clearNo
oauthNo
cookiesNo
headersNo
originsNo
expires_inNo
token_typeNo
access_tokenNo
local_storageNo
refresh_tokenNo
apply_token_asNo
session_storageNo
http_credentialsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the full behavioral burden. It discloses key behaviors: merging semantics, env: variable handling, security note about credentials not being sent to other origins, and auto-refresh for client_credentials/password. It also explains the destructive 'clear' field. While not exhaustive, it covers the most important behavioral traits.

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?

Despite the length, every sentence contributes necessary detail. The format uses line breaks to separate parameter groups, keeping it scannable. The opening sentence establishes purpose, then each line adds a specific explanation. No filler or redundancy; it is appropriately sized for the tool's complexity.

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 tool with 14 parameters and no output schema, the description is remarkably complete. It covers all major parameters, provides examples, defaults, security guidance, and next-step instructions for OAuth flows. It explains side effects and merging behavior. Nothing critical is missing for an agent to call it correctly.

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?

With 0% schema description coverage, the description must fully compensate. It does so admirably: it explains origins with an example and default, enumerates apply_token_as values, details the oauth object structure and flows, specifies cookie formats, and clarifies injection points for local/session storage. This goes far beyond the bare schema property names and adds practical usage context.

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 'Create or update an auth profile,' which is a specific verb+resource statement. It distinguishes itself from siblings like auth_profiles (presumably listing/reading), auth_delete_profile (deletion), and auth_browser_login (interactive login) by clearly indicating its scope is profile creation/update.

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

Usage Guidelines3/5

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

The description gives some contextual guidance (e.g., 'For authorization_code, call auth_oauth_login next'), but it never explicitly states when to use this tool versus alternatives like auth_browser_login or auth_oauth_login for login flows. It implies usage by describing what fields do, but lacks explicit 'use when X, not when Y' guidance.

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