meta-mcp

meta_subscribe_webhook

Subscribe to webhook notifications for Meta objects like Instagram or Page. Provide callback URL, verify token, and fields to receive updates on changes such as messages or feed.

Instructions

Subscribe to webhook notifications for an object (e.g., 'instagram', 'page'). Requires META_APP_ID and META_APP_SECRET.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object": "<object>",
      "callback_url": "<callback_url>",
      "verify_token": "<verify_token>",
      "fields": "<fields>"
    },
    "name": "meta_subscribe_webhook"
  }
}

Input Schema

Name	Required	Description
`fields`	Yes	Comma-separated list of fields to subscribe (e.g., 'messages,feed')
`object`	Yes	Object type to subscribe to
`callback_url`	Yes	HTTPS webhook endpoint URL
`verify_token`	Yes	Verification token for the webhook

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Mar 19, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The description indicates a mutating operation but lacks details on side effects (e.g., behavior if already subscribed, rate limits, or error conditions). Since no annotations are provided, the description carries full burden but only partially fulfills it.

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 sentences, front-loaded with the main verb and resource. No redundant information, every word contributes to clarity.

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 subscription creation tool with 4 required parameters and no output schema, the description covers the core action and prerequisites. Missing details on expected response or post-conditions, but sufficient for basic usage.

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 is 100% with descriptions for each parameter. The description adds value by noting external prerequisites (META_APP_ID, META_APP_SECRET) that are not in the schema, but does not elaborate on parameter usage beyond the schema.

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 action ('Subscribe to webhook notifications') and the resource ('an object (e.g., 'instagram', 'page')'), providing concrete examples. This distinguishes it from sibling tools like 'meta_get_webhook_subscriptions' which is for reading subscriptions.

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?

It explicitly mentions the requirement of META_APP_ID and META_APP_SECRET, which is a clear prerequisite. However, it does not specify when not to use this tool or mention alternatives beyond implying the existence of a get subscriptions tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server