Skip to main content
Glama

session_warmup

Navigate to a target URL with a pre-warmed session to bypass anti-bot detection. Uses natural browsing patterns like visiting the homepage first or following a referer chain.

Instructions

Warm up session by navigating naturally before hitting target URL. Anti-bot systems score trust by session history — direct deep-URL hits look suspicious.

Patterns:
  - homepage_first: goto origin → wait → goto target
  - referer_chain: goto origin → find link to target → click
  - natural_browse: homepage → scroll → random click → scroll → target

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_urlYes
patternNohomepage_first
dwell_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist, so description bears full burden. It explains the natural navigation patterns and their purpose, but does not disclose potential side effects (e.g., session state changes, timeouts, or error handling). The description adds some behavioral context but is not comprehensive.

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?

Description is well-structured with a clear first sentence followed by a bulleted list of patterns. It is concise yet informative, though the pattern list could reference the enum values in the schema to avoid redundancy.

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 presence of an output schema, description does not need to cover return values. However, it omits prerequisites (e.g., existing browser session) and does not explain how dwell_seconds affects behavior. The description covers the 'why' and 'how' patterns but misses some operational details.

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

Parameters2/5

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

Schema description coverage is 0%, but description provides no parameter explanations. Though the schema defines parameters with enums and defaults, the description should add guidance like 'dwell_seconds controls wait time between steps' or clarify pattern choices. This omission limits agent understanding.

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?

Description clearly states the tool's purpose: warming up a session by navigating naturally before hitting a target URL to avoid anti-bot detection. This verb+resource description differentiates it from direct navigation tools like 'navigate'.

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?

Description provides context on when to use this tool (anti-bot systems penalize direct deep-URL hits) and lists three patterns as usage options. It lacks explicit 'when not to use' or alternatives, but the clear context suffices.

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/RobithYusuf/mcp-stealth-chrome'

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