Skip to main content
Glama

Send Offline Conversion Event

meta_send_offline_event

Send offline conversion events to Meta's offline event set to track in-store purchases, phone orders, and other conversions using hashed customer data.

Instructions

Sends an offline conversion event to a Meta offline event set.

Used for tracking in-store purchases, phone orders, or other offline conversions.

Args:

  • event_set_id (string): Offline event set ID (from meta_list_offline_event_sets)

  • event_name (string): Event name (e.g., "Purchase", "Lead")

  • event_time (number): Unix timestamp of the conversion

  • user_data (object): Customer match data — at least one of: email, phone, fn (first name), ln (last name), ct (city), st (state), zip, country, external_id. All PII must be SHA256 hashed.

  • custom_data (object, optional): { currency, value, content_name, order_id }

  • upload_tag (string, optional): Tag for grouping uploads

Returns: Number of events received.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_dataYesCustomer match data (hashed PII)
event_nameYesEvent name (e.g., 'Purchase')
event_timeYesUnix timestamp
upload_tagNoTag for grouping uploads
custom_dataNo
event_set_idYesOffline event set ID
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already indicate a non-read-only, non-destructive write operation. The description adds value by revealing the PII hashing requirement (SHA256) and the return value (number of events received), which are critical for correct use. It does not contradict any annotation.

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?

The description is front-loaded with the core purpose, followed by a clear bullet-like 'Args' list. It packs essential details (format requirements, optional fields, return value) without fluff. Every line contributes to correct invocation.

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

Completeness5/5

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

For a write operation with no output schema, the description covers all necessary aspects: required vs optional args, hashing requirements, return contract, and typical usage scenarios. Given the tool's complexity, the description is sufficiently complete for an agent to call it correctly.

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 high (86%), but the description enriches the `user_data` parameter by specifying the accepted fields and the mandatory hashing rule, which the schema only loosely describes as 'hashed PII.' This goes beyond the schema and helps agents correctly format the payload.

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 opens with a precise verb-resource pairing: 'Sends an offline conversion event to a Meta offline event set.' It also names concrete use cases (in-store purchases, phone orders) that distinguish it from the sibling online conversion tool 'meta_send_conversion_event.'

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 states when to use the tool ('Used for tracking in-store purchases, phone orders, or other offline conversions'), giving clear context. However, it does not explicitly exclude online conversions or mention the alternative 'meta_send_conversion_event,' so the when-not guidance is implicit.

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/open-work-org/open-mcp-servers'

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