Skip to main content
Glama
yinnho

AginxBrowser

by yinnho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust

import_curl

Import a real browser's authenticated session by pasting a 'Copy as cURL' command; returns a live session with cookies and the target URL, so the agent continues without a second login.

Instructions

Import login state from a real browser in one paste. The human logs into a site in their own Chrome (solving the CAPTCHA/SMS once), opens DevTools → Network, right-clicks any authenticated request → "Copy as cURL", and passes the command here. Returns a live session_id already carrying that site's cookies and sitting on the copied request's URL — the agent continues from where the human left off, no password or second login needed. Works with bash, PowerShell and cmd copy flavors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curlYesA "Copy as cURL" command pasted from Chrome DevTools (Network panel → right-click any authenticated request). bash, PowerShell and cmd flavors all parse; the cookie set is injected and the session navigates to the copied request's URL.
accountNoAttach the session to a named account: the imported login lands in the account's private jar and is written back under its name after every action — one import per identity, no clobbering.
use_proxyNoRoute the session's traffic through the engine proxy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.1
    • addedInput schema / properties / account
      Added value: +{
+  "default": null,
+  "description": "Attach the session to a named account: the imported login lands in\nthe account's private jar and is written back under its name after\nevery action — one import per identity, no clobbering.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedInput schema / title
      Removed value: -"ImportCurlParams"
  2. Addedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only provide a title, so the description carries the behavioral burden. It discloses that the tool imports cookies, navigates to the copied request's URL, returns a session_id, and supports multiple shell flavors. It does not mention side effects like session replacement or security warnings, but the core mutation behavior is transparent.

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?

The description is a single, moderately long paragraph but every sentence earns its place. It front-loads the core purpose and then details the workflow and output. Slightly run-on but not wasteful; could be split into bullet points for clarity, but it is effective.

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?

For a 3-param tool with no output schema, the description covers the input format, the expected usage flow, the return value (session_id), and account attachment behavior. It lacks edge-case handling (invalid cURL, overwrite rules) but is complete enough 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the curl param's multi-flavor parsing and the account param's 'private jar' and 'no clobbering' behavior, which clarifies intent beyond the raw property descriptions.

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 verb (import) and resource (login state from a browser via cURL), and distinguishes it from siblings like session_create by framing it as 'Import login state from a real browser in one paste.' It precisely explains what the tool does and how it fits into the session workflow.

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?

The description gives a concrete scenario (human solves CAPTCHA/SMS in Chrome, copies cURL, agent continues) and implicitly positions it as the alternative to manual authentication. However, it does not explicitly name when not to use it or mention alternatives like session_create for fresh sessions, so it stops short of full exclusion guidance.

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