Skip to main content
Glama

meta_ads_conversions_send_purchase

Send a single purchase event to Meta Conversions API with amount, currency, and hashed user identifiers to attribute conversions.

Instructions

Sends a single Purchase event via the Meta Conversions API — the most common CAPI use case. Returns Meta's events_received acknowledgement. Mutating on Meta's side. Required fields model a typical purchase: amount, currency, and hashed user identifiers. For other event types use meta_ads_conversions_send_lead (leads) or the generic meta_ads_conversions_send (AddToCart / custom events / batching multiple events).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
pixel_idYesMeta Pixel ID the event is attributed to. Find via meta_ads_pixels_list. CAPI events flow into the same pixel as browser events; dedupe happens on event_id if one is supplied in user_data / custom_data.
event_timeYesUNIX timestamp (seconds) of the purchase. Must be within the last 7 days.
user_dataYesUser identifying fields for attribution. Supported keys: em (email), ph (phone), fn (first_name), ln (last_name), zp (zip), ct (city), st (state), country, external_id, client_ip_address, client_user_agent, fbc (click ID), fbp (browser ID). mureo hashes em / ph / fn / ln / zp / ct / st / country / external_id with SHA-256 before sending — pass raw PII; do not pre-hash.
currencyYesISO 4217 currency code (USD, JPY, EUR, GBP). Must match the ad account's reporting currency or be one that Meta can convert.
valueYesPurchase amount in the specified currency. Decimal for currencies with minor units (USD 9.99); integer is fine for JPY.
content_idsNoProduct IDs associated with the purchase — catalog retailer_ids for DPA attribution. Optional but recommended when a catalog is in use.
event_source_urlNoFully-qualified URL where the event occurred. Required by Meta for action_source='website' events; recommended for any browser-triggered CAPI event to improve attribution match rate.
test_event_codeNoMeta Events Manager test_event_code. When set, the event is routed to the test event stream visible in Events Manager instead of production reporting. Use for validation; drop the field once verified. Get the code from Events Manager → Test Events tab.
Behavior4/5

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

With no annotations, the description carries the full burden. It notes 'Mutating on Meta's side' and explains that user data is hashed via SHA-256. It states the return is an acknowledgement. Could mention deduplication or rate limits, but overall provides good behavioral context.

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 four sentences, each serving a clear purpose: purpose, return type, mutating nature, and sibling differentiation. No redundant words.

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?

Given the complexity (9 params, nested objects, no output schema), the description covers purpose, usage, and alternatives. It could add error handling or prerequisites, but the schema fills in parameter details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 no extra meaning beyond the schema's detailed parameter descriptions; it only summarizes that required fields model a typical purchase.

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 explicitly states the verb 'sends a single Purchase event' and identifies the resource (Meta Conversions API). It distinguishes from siblings by naming meta_ads_conversions_send_lead and meta_ads_conversions_send for other event types.

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?

The description clearly states when to use this tool (for Purchase events) and when not to, by directing to alternatives for leads or custom events. It also explains that it returns an acknowledgement.

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/logly/mureo'

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