Skip to main content
Glama
aruxojuyu665

Manus MCP

by aruxojuyu665
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

manus_browser_online_list

Lists available online browser clients. Use the returned client_id with manus_task_confirm_action when the agent requests a browser connection. An empty list indicates the Manus Browser Extension is not installed or enabled.

Instructions

List online browser clients. Use the returned client_id with manus_task_confirm_action when the agent triggers a needConnectMyBrowser waiting event. Empty list means you need to install/enable the Manus Browser Extension.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • manus_mcp/tools/browser.py:9-25 (handler)
    The handler function for the 'manus_browser_online_list' tool. Decorated with @manus_tool, it makes a GET request to /v2/browser.onlineList and returns a BrowserOnlineListResponse.
    @manus_tool(
    name="manus_browser_online_list",
    description=(
        "List online browser clients. Use the returned client_id with manus_task_confirm_action "
        "when the agent triggers a needConnectMyBrowser waiting event. Empty list means you need "
        "to install/enable the Manus Browser Extension."
    ),
    input_schema=BrowserOnlineListQuery,
    output_schema=BrowserOnlineListResponse,
)
async def browser_online_list(q: BrowserOnlineListQuery, ctx: ToolCtx) -> BrowserOnlineListResponse:
    return await ctx.client.call(
        "GET",
        "/v2/browser.onlineList",
        response_model=BrowserOnlineListResponse,
        rate_limit_key="browser.onlineList",
    )
  • manus_mcp/schemas/browser.py:17-18 (schema)
    Input schema (BrowserOnlineListQuery) – an empty model with no required fields.
    class BrowserOnlineListQuery(ManusModel):
    pass
  • manus_mcp/schemas/browser.py:21-22 (schema)
    Output schema (BrowserOnlineListResponse) – extends ResponseEnvelope with a 'data' field containing a list of BrowserClient objects.
    class BrowserOnlineListResponse(ResponseEnvelope):
    data: list[BrowserClient] = []
  • manus_mcp/schemas/browser.py:10-14 (schema)
    BrowserClient model – used as the item type in the response's data list. Fields: client_id (required), client_name, ua.
    class BrowserClient(ManusModel):
    model_config = ConfigDict(extra="allow")
    client_id: str
    client_name: str | None = None
    ua: str | None = None
  • manus_mcp/tools/browser.py:9-18 (registration)
    Registration via @manus_tool decorator: name='manus_browser_online_list', with description, input_schema=BrowserOnlineListQuery, output_schema=BrowserOnlineListResponse. The decorator in registry.py adds a ToolDef to the _REGISTRY dict.
    @manus_tool(
    name="manus_browser_online_list",
    description=(
        "List online browser clients. Use the returned client_id with manus_task_confirm_action "
        "when the agent triggers a needConnectMyBrowser waiting event. Empty list means you need "
        "to install/enable the Manus Browser Extension."
    ),
    input_schema=BrowserOnlineListQuery,
    output_schema=BrowserOnlineListResponse,
)

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations provided, so the description must carry full weight. It reveals that an empty list means the extension needs installation and explains the relationship with the confirm action. Though it doesn't mention side effects or read-only nature, the tool is inherently a list operation.

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 two sentences, front-loaded with the main action, and contains no unnecessary words. Every sentence provides essential 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?

For a simple tool with no parameters and no output schema, the description adequately covers the return value (client_id) and explains the empty list case. It is complete for its purpose, though it could optionally mention if there are any prerequisites.

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?

The input schema has no parameters, so the baseline is 4. The description adds value by explaining how the returned client_id is used, which is beyond schema information.

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's purpose: 'List online browser clients.' It specifies the intended use in the workflow (when a needConnectMyBrowser waiting event occurs) and distinguishes itself from sibling tools like task confirmation 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 explicitly tells when to use the tool (when a needConnectMyBrowser waiting event triggers) and what to do with the result (use the client_id with manus_task_confirm_action). It does not explicitly mention when not to use it, but the context is clear.

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/aruxojuyu665/Manus-MCP'

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