Skip to main content
Glama

manus_webhook_create

Register an HTTPS webhook to receive task_created and task_stopped events from Manus. Your endpoint must return a 2xx status within 10 seconds after a test request is sent for activation.

Instructions

Register an HTTPS webhook URL to receive task_created and task_stopped events. Manus sends a test request before activation; endpoint must return 2xx within 10 seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Implementation Reference

  • Handler function for manus_webhook_create tool; makes a POST /v2/webhook.create API call with the URL from WebhookCreateRequest.
    @manus_tool(
        name="manus_webhook_create",
        description=(
            "Register an HTTPS webhook URL to receive task_created and task_stopped events. "
            "Manus sends a test request before activation; endpoint must return 2xx within 10 seconds."
        ),
        input_schema=WebhookCreateRequest,
        output_schema=WebhookCreateResponse,
    )
    async def webhook_create(req: WebhookCreateRequest, ctx: ToolCtx) -> WebhookCreateResponse:
        return await ctx.client.call(
            "POST",
            "/v2/webhook.create",
            json_body=req,
            response_model=WebhookCreateResponse,
            rate_limit_key="webhook.create",
        )
  • Input schema (WebhookCreateRequest with url field) and output schema (WebhookCreateResponse with webhook record) for the tool.
    class WebhookCreateRequest(ManusModel):
        url: str
    
    
    class WebhookCreateResponse(ResponseEnvelope):
        webhook: WebhookRecord
  • The @manus_tool decorator and ToolDef/ToolCtx types used by the registry to register manus_webhook_create.
    class ToolDef(Generic[TIn, TOut]):
        """Metadata + handler for a single MCP tool."""
    
        name: str
        description: str
        input_schema: type[TIn]
        output_schema: type[TOut]
        handler: Callable[[TIn, ToolCtx], Awaitable[TOut]]
        rate_limit_key: str | None = None
    
    
    _REGISTRY: dict[str, ToolDef[Any, Any]] = {}
    
    
    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
  • load_all_tool_modules import of webhooks module which triggers @manus_tool registration of manus_webhook_create.
    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
  • WebhookRecord model used in WebhookCreateResponse to represent the created webhook.
    class WebhookRecord(ManusModel):
        model_config = ConfigDict(extra="allow")
        id: str
        url: str
        status: WebhookStatus | None = None
        created_at: UnixSeconds | None = None
    
    
    class WebhookCreateRequest(ManusModel):
        url: str
    
    
    class WebhookCreateResponse(ResponseEnvelope):
        webhook: WebhookRecord
    
    
    class WebhookListQuery(ManusModel):
        pass
    
    
    class WebhookListResponse(ResponseEnvelope):
        data: list[WebhookRecord] = []
    
    
    class WebhookDeleteRequest(ManusModel):
        webhook_id: str
    
    
    class WebhookDeleteResponse(ResponseEnvelope):
        pass
    
    
    class WebhookPublicKeyQuery(ManusModel):
        pass
    
    
    class WebhookPublicKeyResponse(ResponseEnvelope):
        public_key: str
        algorithm: str | None = None
Behavior3/5

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

With no annotations, the description discloses the key behavior of a test request and required 2xx response within 10 seconds. It does not cover failure handling, idempotency, or limits, but for a simple creation tool this is adequate.

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 concise sentences with no redundant information. Every part is essential for understanding the tool's function and key behavior.

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?

Given the tool's simplicity (1 param, no output schema), the description covers the primary purpose and critical behavior. It lacks return value details but is sufficient for an agent to select and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'url' has no schema description. The description adds minimal value by implying HTTPS is required, but does not specify format, allowed protocols, or path restrictions. Schema description coverage is 0%, so the description should compensate more.

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 registers an HTTPS webhook to receive task_created and task_stopped events. This verb+resource specification distinguishes it from sibling tools like webhook_delete, webhook_list, and webhook_events_*.

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 mentions the test request and timeout, which provides essential usage guidance. However, it does not explicitly state when to use this tool vs alternatives (e.g., updating an existing webhook), and lacks prerequisites like server readiness.

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