Skip to main content
Glama

manus_webhook_list

Retrieve a list of all registered webhooks. Use this to view current webhook configurations and manage integrations.

Instructions

List all registered webhooks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `webhook_list` async handler function decorated with @manus_tool(name='manus_webhook_list'). It calls the Manus API GET /v2/webhook.list and returns a WebhookListResponse. This is the core logic of the tool.
    @manus_tool(
        name="manus_webhook_list",
        description="List all registered webhooks.",
        input_schema=WebhookListQuery,
        output_schema=WebhookListResponse,
    )
    async def webhook_list(q: WebhookListQuery, ctx: ToolCtx) -> WebhookListResponse:
        return await ctx.client.call(
            "GET",
            "/v2/webhook.list",
            response_model=WebhookListResponse,
            rate_limit_key="webhook.list",
        )
  • Input schema `WebhookListQuery` (empty, no required fields) and output schema `WebhookListResponse` (wraps a list of `WebhookRecord` in a `ResponseEnvelope`).
    class WebhookListQuery(ManusModel):
        pass
    
    
    class WebhookListResponse(ResponseEnvelope):
        data: list[WebhookRecord] = []
  • The `manus_tool` decorator that registers the tool in `_REGISTRY` when the decorator fires at import time. This is how 'manus_webhook_list' gets registered as a ToolDef.
    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
  • The `load_all_tool_modules()` function imports the `webhooks` module (among others), which triggers the @manus_tool decorator to fire and register 'manus_webhook_list'.
    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
Behavior2/5

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

The description only implies a read-only, non-destructive operation by using 'List'. No annotations are present, so the description carries full burden. It does not disclose pagination, rate limits, authentication requirements, or return format. This is minimal for 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 a single, front-loaded sentence of just 4 words. Every word is meaningful, and there is no wasted text. It is as concise as possible while still conveying the tool's purpose.

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 operation with no parameters and no output schema, the description is fairly complete. It states what the tool does and the scope (all webhooks). However, it could optionally mention that it returns a list or that it is a read-only operation. Still, it is adequate for the tool's simplicity.

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 zero parameters and schema description coverage is 100%. According to the rubric, 0 parameters yields a baseline of 4. The description adds 'all registered webhooks' which confirms the scope but does not add further meaning. Since there are no parameters, no additional semantics are needed.

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 uses a specific verb ('List') and resource ('registered webhooks'), clearly distinguishing it from sibling tools like manus_webhook_create or manus_webhook_delete. It leaves no ambiguity about what the tool does.

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?

The description provides no guidance on when to use this tool versus alternatives, such as manus_webhook_events_list or manus_webhook_detail. No context on prerequisites or usage conditions is given.

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