Skip to main content
Glama

⚠️ Register webhook receiver

messenger_register_webhook
Destructive

Subscribes Avito to a webhook URL to receive messenger events. Registers the URL from server configuration so new chat messages flow automatically.

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. Keys are stored as bounded SHA-256 fingerprints.
Behavior5/5

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

Discloses additive nature, auto-fill from config, public internet requirement, and idempotency behavior. Annotations indicate destructiveHint=true and idempotentHint=false, which are consistent with description. Adds context beyond annotations, such as no deletion of other subscriptions.

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?

Description is comprehensive but slightly long. Each sentence serves a purpose: core action, behavioral notes, comparison to sibling, and related tools. Well-structured with clear ordering, though could be tightened slightly.

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?

No output schema exists; the description does not specify the return value for a non-dry-run call. It also does not cover error conditions or what happens if the URL is invalid. For a registration tool, some additional detail on response and failure modes would improve completeness.

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?

All three parameters are fully described in the schema (100% coverage). The description adds value by explaining the auto-fill behavior for url, the preview functionality for dryRun, and duplicate protection for idempotencyKey. This goes beyond the schema descriptions.

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 it subscribes Avito to a webhook URL for messenger events, distinguishes from sibling messenger_post_webhook_v3 by auto-fill feature, and mentions related tools for reading/unsubscribing. Verb and resource are specific.

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 states when to use (to receive events), what it does not do (no deletion of existing subscriptions), prerequisites (public HTTPS address), alternatives (manual URL via v3, unsubscribe via another tool), and related functions (get_events, get_status). Covers both usage and exclusion.

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