Skip to main content
Glama

Send Conversion Event (CAPI)

meta_send_conversion_event

Send server-side conversion events to Meta using the Conversions API. Supports standard and custom events with deduplication for accurate attribution.

Instructions

Sends a server-side conversion event to Meta via the Conversions API.

Args:

  • pixel_id: Meta Pixel ID

  • event_name: Standard events: Purchase, Lead, AddToCart, CompleteRegistration, ViewContent, Search, InitiateCheckout, AddPaymentInfo, AddToWishlist, Subscribe, StartTrial, Contact, CustomizeProduct, Donate, FindLocation, Schedule, SubmitApplication, PageView. Custom event names also accepted.

  • event_time: Unix timestamp

  • event_source_url (optional): URL where conversion happened

  • user_data: At minimum one of: em (hashed email), ph (hashed phone), fbc, fbp, client_ip_address, client_user_agent, external_id

  • custom_data (optional): { currency, value, content_name, content_ids, content_type, order_id, num_items }

  • event_id (optional): For deduplication with browser pixel

  • action_source: "website", "app", "email", "phone_call", "chat", "physical_store", "system_generated", "business_messaging", "other"

  • test_event_code (optional): For testing without affecting production data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pixel_idYesMeta Pixel ID
event_nameYesConversion event name. Standard events: Purchase, Lead, AddToCart, CompleteRegistration, ViewContent, Search, InitiateCheckout, AddPaymentInfo, AddToWishlist, Subscribe, StartTrial, Contact, CustomizeProduct, Donate, FindLocation, Schedule, SubmitApplication, PageView. Custom event names are also accepted.
event_timeYesUnix timestamp of the event
event_source_urlNoURL where conversion happened
user_dataYesUser data for matching (at least one identifier required — more fields = better match rate)
custom_dataNoCustom event data
event_idNoDeduplication ID (matches browser pixel)
action_sourceYesWhere the conversion originated
test_event_codeNoTest event code (won't affect production data)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior3/5

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

Annotations indicate a write operation (readOnlyHint=false) but not destructive. The description adds context about deduplication via event_id but does not disclose rate limits, error handling, or authentication needs. It does not contradict annotations.

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

Conciseness3/5

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

The description uses a list format for parameters, which is structured, but it is somewhat lengthy. Each line adds information, but the overall length could be reduced without losing clarity. It is acceptable but not optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 10 parameters including nested objects, and no output schema. The description fails to explain the return value or response format (despite a response_format parameter in the schema). It does not cover error handling or success indicators, leaving agents without critical usage context.

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%, so baseline is 3. The description adds critical constraints not in the schema, such as 'at minimum one of: em, ph, fbc, fbp, client_ip_address, client_user_agent, external_id' for user_data, and lists standard event names. This compensates for the schema's lack of requirement specification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it sends a server-side conversion event via the Conversions API, with a specific verb and resource. The title adds context. However, it does not explicitly differentiate from sibling tools like meta_send_offline_event or meta_test_conversion_events, leaving some ambiguity.

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?

No guidance on when to use this tool versus alternatives such as meta_send_offline_event or meta_test_conversion_events. The description does not include when to use, when not to use, or prerequisites, which is a significant gap for an agent selecting tools.

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/oliverames/meta-mcp-server'

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