Skip to main content
Glama

⚠️ Register webhook receiver

messenger_register_webhook

Registers a webhook subscription to forward new Avito chat messages to the configured public URL, enabling event reception.

Instructions

Subscribes Avito to THIS server's configured webhook receiver URL so messenger events (new chat messages) start flowing. Registers only the URL derived from the webhook config (AVITO_MCP_WEBHOOK_PUBLIC_URL + path + secret). Adds a webhook subscription (additive — it does not delete other subscriptions); Avito will then POST events to the URL (requires a PUBLIC HTTPS address reachable from the internet; localhost does not work). Same operation as messenger_post_webhook_v3, but auto-fills the URL from config. Pairs with messenger_get_webhook_events (read received events) and messenger_get_webhook_status (receiver config). To unsubscribe, use messenger_post_webhook_unsubscribe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoOptional explicit copy of the configured receiver URL Avito should POST events to. For safety, it must equal publicUrl + path + secret; omit to auto-fill it.
dryRunNov0.7.0: if true — returns a preview of the HTTP request without calling the Avito API. Safe for inspecting exactly what would be done. Default: the value of AVITO_MCP_DRY_RUN_DEFAULT (usually false).
idempotencyKeyNov0.7.0: optional key for duplicate protection. A repeat call with the same key within AVITO_MCP_IDEMPOTENCY_TTL_SEC returns the cached result. The same key with different args returns a conflict error — this is safe by design.
Behavior4/5

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

Annotations already indicate non-read-only, non-destructive, non-idempotent, open-world. Description adds additive behavior, URL auto-fill, and public HTTPS requirement. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Multiple sentences but each serves a purpose. Front-loaded with main action, then details, comparisons, and related tools. Could be slightly tighter but well-structured.

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?

Covers main behavior, prerequisites, alternatives, and related tools. No output schema so response format not needed. Adequate for agent decision-making given three optional parameters.

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 coverage 100% so baseline 3. Description adds meaning: url 'omit to auto-fill', dryRun 'preview without calling API', idempotencyKey explains duplicate protection and conflict handling.

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 the tool subscribes Avito to a webhook receiver URL for messenger events, using specific verbs 'Subscribes' and 'Registers'. It distinguishes from sibling messenger_post_webhook_v3 by noting auto-fill from config.

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

Usage Guidelines5/5

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

Explicitly compares to messenger_post_webhook_v3, provides alternatives (unsubscribe tool), mentions required pairing tools (get_webhook_events, get_webhook_status), and warns about public HTTPS requirement.

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/elchin92/avito-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server