Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_conversion_event

Send a server-side conversion event through the Meta Conversions API (pixel) to track actions like purchases or leads, with support for test event codes to verify delivery.

Instructions

Send a server-side conversion event via the Conversions API (pixel).

Input Schema

NameRequiredDescriptionDefault
eventsYesJSON array of events: [{event_name, event_time, user_data, custom_data, action_source}]
test_event_codeNoEvents Manager test code; use to verify delivery as test events

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / test_event_code
      Added value: +{
+  "description": "Events Manager test code; use to verify delivery as test events",
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Since no annotations were provided, the description carries the full burden of behavioral context. Stating it uses the 'Conversions API (pixel)' is a vital piece of operational information that defines how the event is processed and where the data originates (server-side vs. web). This goes beyond merely stating 'send event'.

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 definition is a single, highly focused sentence. It immediately states the action and its constraints without any superfluous language, making it maximally concise and efficiently structured.

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 service endpoint defined by a specific API (Conversions API), the definition is nearly complete. It clearly defines the action and the input requirements (including the structure of the event payload). The omission of rate limits or specific error handling is a minor gap, especially given the lack of annotations.

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?

Although the schema coverage is 100%, the description adds crucial semantic meaning by detailing the required structure of the 'events' parameter: 'JSON array of events: [{event_name, event_time, user_data, custom_data, action_source}]'. This clarifies the payload composition beyond a generic 'string' type.

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 specific action ('Send a server-side conversion event') and specifies the delivery mechanism ('via the Conversions API (pixel)'). This high specificity allows an agent to differentiate it from other generic event sending tools, such as send_offline_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 specifies the scope and mechanism ('server-side conversion event via the Conversions API'), implicitly guiding the agent toward its correct use case and away from client-side or less integrated alternatives. While it doesn't explicitly name alternatives, the contextual guidance is very clear.

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

Deploy Server

Other Tools