Skip to main content
Glama
Oliver0804

cloakbrowser-mcp

by Oliver0804

cloak_interact

Execute a sequence of browser actions (goto, click, fill) and extract text or HTML from the final page.

Instructions

在單一 session 內依序執行多個瀏覽器動作,最後擷取結果。

actions 是動作清單,第一個通常是 goto。每個動作是一個 dict,type 可為: {"type":"goto","url":"...","wait_until":"domcontentloaded"} {"type":"click","selector":"button#login"} {"type":"fill","selector":"#email","value":"a@b.com"} {"type":"type","selector":"#q","value":"hello","delay":40} {"type":"press","selector":"#q","keys":"Enter"} {"type":"select","selector":"#country","value":"TW"} {"type":"scroll","dy":1500} {"type":"wait_selector","selector":".results","timeout_ms":15000} {"type":"wait_ms","ms":1500}

extract: text | html | none(最終要回傳的內容形式)。 selector: extract=text 時只取此元素文字。 screenshot_path: 給定則動作跑完後再截一張整頁圖。 其餘反偵測參數同 cloak_get_text;表單 / 登入流程建議 humanize=True。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionsYes
extractNotext
selectorNo
screenshot_pathNo
timeout_msNo
max_charsNo
humanizeNo
headlessNo
proxyNo
geoipNo
timezoneNo
localeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Details action types, extraction modes, anti-detection parameters, and humanization. No annotations exist, so description carries burden. Missing some edge-case behavior like error handling or session lifecycle, but generally thorough.

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?

Well-structured with bullet-pointed action types. A bit lengthy but every part adds value. No redundant information.

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 12 parameters and complexity, description covers core functionality. References sibling for anti-detection details. Has output schema so return values not needed. Minor gaps like missing timeout_ms details.

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 0%, but description explains actions format, extract, selector, screenshot_path, humanize, headless, proxy, etc. Timeout_ms and max_chars are not explained, but overall adds significant meaning beyond 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 it executes a sequence of browser actions and extracts results. It differentiates from sibling tools which are for direct extraction, establishing a distinct purpose.

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?

Provides guidance such as 'first action is usually goto' and suggests humanize=True for forms. However, lacks explicit when-to-use vs when-not-to-use compared to siblings.

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/Oliver0804/cloakbrowser-mcp'

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