Skip to main content
Glama

http_request

Send HTTP requests with authentic browser TLS fingerprints to scrape APIs using authenticated sessions from active browser tabs.

Instructions

HTTP request with TLS-perfect browser fingerprint via curl_cffi. Use for API scraping after browser login — same stealth as real Chrome's JA3/JA4.

Args:
    url, method: target URL and HTTP verb
    impersonate: chrome, chrome124, firefox, safari, edge (default chrome)
    use_browser_cookies: auto-inject cookies from active browser tab
    headers, params: extra headers/query params
    data: raw body string (form-urlencoded or custom)
    json_body: JSON body dict (sets Content-Type automatically)
    timeout, follow_redirects: usual HTTP options
    return_mode: auto (json if parseable else text), json, text, or meta (status+headers only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
methodNoGET
impersonateNochrome
use_browser_cookiesNo
headersNo
paramsNo
dataNo
json_bodyNo
timeoutNo
follow_redirectsNo
return_modeNoauto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the burden. It explains the stealth fingerprinting and cookie injection behavior but does not disclose error handling, rate limiting, or the stateless nature beyond schema defaults.

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 concise, with a clear purpose statement followed by a well-structured list of arguments. Every sentence adds value without redundancy.

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?

Given the complexity of 11 parameters and presence of an output schema, the description thoroughly covers input semantics and purpose, making it complete for an agent to invoke 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 explains all 11 parameters in detail, including allowed values for impersonate, behavior of use_browser_cookies, and options for return_mode. This adds significant value beyond the 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 clearly states the tool makes HTTP requests with TLS-perfect browser fingerprinting via curl_cffi, explicitly for API scraping after browser login. It distinguishes from sibling tools like http_request_with_session by focusing on stealth and single requests.

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 advises 'Use for API scraping after browser login' but does not explicitly contrast with alternatives or mention when not to use it. Guidance is present but could be more precise.

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