Skip to main content
Glama

manus_connector_list

List all connectors installed in your account and obtain their IDs for use in creating tasks or sending messages.

Instructions

List all connectors installed in the account. Use the returned IDs in the connectors array of manus_task_create / manus_task_send_message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async function `connector_list` is the handler for the 'manus_connector_list' tool. It makes a GET request to /v2/connector.list using the client and returns the response.
    async def connector_list(q: ConnectorListQuery, ctx: ToolCtx) -> ConnectorListResponse:
        return await ctx.client.call(
            "GET",
            "/v2/connector.list",
            response_model=ConnectorListResponse,
            rate_limit_key="connector.list",
        )
  • ConnectorListQuery and ConnectorListResponse define the input/output schemas for the tool. The query takes no parameters; the response contains a list of ConnectorRecords.
    class ConnectorListQuery(ManusModel):
        pass
    
    
    class ConnectorListResponse(ResponseEnvelope):
        data: list[ConnectorRecord] = []
  • ConnectorRecord model represents a single connector with id, name, type, description, and category fields.
    class ConnectorRecord(ManusModel):
        model_config = ConfigDict(extra="allow")
        id: str
        name: str | None = None
        type: ConnectorType | None = None
        description: str | None = None
        category: str | None = None
  • The @manus_tool decorator registers the function as 'manus_connector_list' with description, input_schema=ConnectorListQuery, and output_schema=ConnectorListResponse.
    @manus_tool(
        name="manus_connector_list",
        description=(
            "List all connectors installed in the account. Use the returned IDs in the connectors "
            "array of manus_task_create / manus_task_send_message."
        ),
        input_schema=ConnectorListQuery,
        output_schema=ConnectorListResponse,
    )
  • load_all_tool_modules() imports the connectors module, which triggers the @manus_tool decorator and registers the tool.
    def load_all_tool_modules() -> None:
        """Import every tool module so @manus_tool decorators fire."""
        from manus_mcp.tools import (  # noqa: F401
            agents,
            browser,
            composite,
            connectors,
            files,
            projects,
            skills,
            tasks,
            usage,
            webhooks,
            website,
        )
        from manus_mcp.webhook_receiver import tools as _webhook_receiver_tools  # noqa: F401
Behavior4/5

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

With no annotations, the description correctly indicates a read-only list operation. It does not detail permissions, pagination, or side effects, but the behavior is straightforward given zero parameters and simple listing.

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?

Two sentences: first states purpose, second provides usage guidance. No extraneous information, front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks description of the output structure (e.g., array of connector objects). While usage guidance helps, the absence of output schema means more detail on return format would improve 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 has no parameters (100% coverage), so the description adds value beyond the schema by explaining the returned IDs' purpose. Baseline is 4 for zero-parameter tools.

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 'List all connectors installed in the account' with a specific verb and resource. It distinguishes from sibling tools by explaining how the returned IDs are used in manus_task_create/manus_task_send_message.

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?

Explicitly instructs to use the returned IDs in the connectors array of terkait task tools, providing clear context for when to invoke this tool. Does not mention exclusions or alternatives, but the guidance is sufficient for a list tool.

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