Skip to main content
Glama

manus_skill_list

Retrieve available skills, showing global user skills and optionally adding project-specific skills by supplying a project ID.

Instructions

List available skills. Provide project_id to include project-specific skills in addition to global user skills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNo

Implementation Reference

  • The actual handler function for the 'manus_skill_list' tool. It calls the '/v2/skill.list' API endpoint via the Manus client.
    async def skill_list(q: SkillListQuery, ctx: ToolCtx) -> SkillListResponse:
        return await ctx.client.call(
            "GET",
            "/v2/skill.list",
            params=q.model_dump(exclude_none=True),
            response_model=SkillListResponse,
            rate_limit_key="skill.list",
        )
  • Input schema (SkillListQuery) - accepts an optional project_id parameter.
    class SkillListQuery(ManusModel):
        project_id: str | None = None
  • Output schema (SkillListResponse) - returns a list of SkillRecord objects.
    class SkillListResponse(ResponseEnvelope):
        data: list[SkillRecord] = []
  • The @manus_tool decorator that registers 'manus_skill_list' with its name, description, input_schema, and output_schema into the global tool registry.
    @manus_tool(
        name="manus_skill_list",
        description=(
            "List available skills. Provide project_id to include project-specific skills "
            "in addition to global user skills."
        ),
        input_schema=SkillListQuery,
        output_schema=SkillListResponse,
    )
  • The manus_tool decorator implementation that stores the ToolDef entry in the _REGISTRY dict by tool name.
    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 are provided, so the description carries full burden. It indicates a read-only list operation ('list available skills'), but does not disclose any behavioral traits such as authentication requirements, rate limits, error handling, or scope of 'available skills'. This is 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?

Two short, clear sentences with no redundancy. The first sentence states the action, the second explains the optional parameter. Every word is necessary; no fluff.

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 list tool with one optional parameter and no output schema, the description covers purpose and parameter semantics adequately. However, it could mention what 'available skills' entails (e.g., user-accessible skills) and any sorting or filtering. It is nearly complete but leaves minor gaps.

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 adds meaning by explaining that omitting project_id lists global user skills, and providing it includes project-specific skills. This clarifies the parameter's effect beyond the bare schema definition.

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 available skills' with a specific verb and resource. It distinguishes from sibling list tools (e.g., manus_agent_list, manus_project_list) by focusing on skills, and the mention of project-specific vs global user skills adds precision.

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

Usage Guidelines3/5

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

The description implies usage by stating 'Provide project_id to include project-specific skills', but does not explicitly say when to use this tool vs alternatives or provide any exclusion criteria. No sibling tools compete directly for listing skills, so the lack of explicit when-not is acceptable but not helpful.

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