Skip to main content
Glama

manus_project_list

Retrieve a list of all projects accessible to the authenticated user for project management and oversight.

Instructions

List all projects visible to the current user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for manus_project_list tool. It sends a GET request to /v2/project.list via the client and returns a ProjectListResponse.
    @manus_tool(
        name="manus_project_list",
        description="List all projects visible to the current user.",
        input_schema=ProjectListQuery,
        output_schema=ProjectListResponse,
    )
    async def project_list(q: ProjectListQuery, ctx: ToolCtx) -> ProjectListResponse:
        return await ctx.client.call(
            "GET",
            "/v2/project.list",
            response_model=ProjectListResponse,
            rate_limit_key="project.list",
        )
  • Input schema (ProjectListQuery - empty model with no required fields) and output schema (ProjectListResponse containing a list of ProjectRecord) for the manus_project_list tool.
    class ProjectListQuery(ManusModel):
        pass
    
    
    class ProjectListResponse(ResponseEnvelope):
        data: list[ProjectRecord] = []
  • Tool registration via @manus_tool decorator with name='manus_project_list', description, input_schema=ProjectListQuery, output_schema=ProjectListResponse.
    @manus_tool(
        name="manus_project_list",
        description="List all projects visible to the current user.",
        input_schema=ProjectListQuery,
        output_schema=ProjectListResponse,
    )
  • The projects module is imported in load_all_tool_modules(), causing the @manus_tool decorator to fire and register manus_project_list.
    projects,
  • The @manus_tool decorator registry that stores the tool definition (including the handler) into a global _REGISTRY dict.
    def manus_tool(
        *,
        name: str,
        description: str,
        input_schema: type[TIn],
        output_schema: type[TOut],
        rate_limit_key: str | None = None,
    ) -> Callable[
        [Callable[[TIn, ToolCtx], Awaitable[TOut]]], Callable[[TIn, ToolCtx], Awaitable[TOut]]
    ]:
        """Decorator registering `handler` as a tool with the given metadata."""
    
        def wrap(
            handler: Callable[[TIn, ToolCtx], Awaitable[TOut]],
        ) -> Callable[[TIn, ToolCtx], Awaitable[TOut]]:
            if name in _REGISTRY:
                raise RuntimeError(f"Duplicate tool name: {name}")
            _REGISTRY[name] = ToolDef(
                name=name,
                description=description,
                input_schema=input_schema,
                output_schema=output_schema,
                handler=handler,
                rate_limit_key=rate_limit_key,
            )
            return handler
    
        return wrap
Behavior2/5

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

No annotations provided, and description only states basic read operation. Does not disclose behavioral traits like rate limits, pagination, or side effects. Minimal transparency.

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?

Single sentence, front-loaded, no wasted words. Appropriately sized for a simple list tool.

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?

Adequate for a basic list operation, but lacks hints about output format, pagination, or ordering. Could be more complete given no output schema.

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?

No parameters in schema (0 params), so description does not need to add parameter info. Baseline 4 applies as per rule for zero parameters.

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?

Description clearly states verb 'List', resource 'projects', and scope 'visible to current user'. It distinguishes from sibling tools like manus_project_create.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use versus alternative list tools (e.g., manus_agent_list, manus_task_list). Does not mention prerequisites or context.

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