Skip to main content
Glama

browser_solve_captcha

Solve captchas on the current page by detecting type and site key, then inject the token using a configured provider.

Instructions

Solve a captcha on the current page and inject the token (no extension).

    kind: 'turnstile' | 'recaptcha_v2' | 'recaptcha_v3' | 'hcaptcha' | 'funcaptcha'.
    website_key is auto-detected from the DOM if omitted (for FunCaptcha that's the
    public key). provider defaults to the configured one (needs that provider's API
    key in the environment). Returns the solved token.

    recaptcha_v3: pass page_action (must match the site's grecaptcha.execute action)
      and optionally min_score (0.1–0.9); the token is injected and grecaptcha.execute
      is overridden to return it.
    funcaptcha (Arkose): funcaptcha_subdomain (the Arkose 'surl') and funcaptcha_data
      (the dynamic 'blob' JSON string) are passed through for sites that require them.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoturnstile
website_keyNo
providerNo
session_idNo
page_actionNo
min_scoreNo
funcaptcha_subdomainNo
funcaptcha_dataNo
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description must cover behavioral aspects. It explains auto-detection of website_key, token injection, overriding of grecaptcha.execute for recaptcha_v3, and dependence on provider API key. It does not explicitly state if the operation is read/write or side effects, but the injection implies mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but structured by captcha type. It contains detailed per-kind instructions that could be somewhat redundant. The main purpose is front-loaded, but it could be more concise.

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?

Given the tool's complexity (multiple captcha types) and the existence of an output schema, the description covers input parameters and behavior well. It mentions the returned token. However, it does not discuss error cases or failure modes, which would enhance completeness.

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 description coverage is 0%, so the description must compensate. It explains the kind parameter with enum values, auto-detection of website_key, default provider, recaptcha_v3-specific page_action and min_score, and funcaptcha subdomain/data. Parameters like session_id and timeout are not explained, but timeout has a clear default.

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 solves a captcha and injects the token. The name 'browser_solve_captcha' plus the description make the purpose unambiguous, and it is distinct from all sibling browser tools.

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 provides detailed usage guidance for different captcha kinds (turnstile, recaptcha_v2/v3, hcaptcha, funcaptcha), including when to pass specific parameters like page_action and funcaptcha data. It does not explicitly state when not to use this tool, but the context is clear given its unique function.

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/Evil-Bane/eyebrowse'

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