Skip to main content
Glama

Test Conversion Event (CAPI)

meta_test_conversion_events

Test your Meta Conversions API setup by sending a test conversion event that does not affect production data. Use it to validate event configuration.

Instructions

Tests CAPI setup by sending a test event that won't affect production data.

Same args as meta_send_conversion_event but auto-sets a test_event_code if not provided. Use the test_event_code from Events Manager > Test Events tab.

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
Behavior4/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds value by stating the test event 'won't affect production data' (consistent with destructiveHint=false) and that it 'auto-sets a test_event_code if not provided.' No contradictions.

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 concise: two sentences plus a line about arguments. It front-loads the purpose and provides essential guidance without unnecessary detail.

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

Completeness3/5

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

The tool has no output schema. While the description covers purpose and usage, it does not explain the return value or response format. The response_format parameter is documented in schema, but the description could be more complete about what the agent will receive after sending the test event.

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% with detailed parameter descriptions. The description does not add new parameter semantics beyond stating 'Same args as meta_send_conversion_event.' Baseline 3 is appropriate given high schema coverage.

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 tool's purpose: 'Tests CAPI setup by sending a test event that won't affect production data.' It specifies the verb (test) and the resource (CAPI setup via test event), and distinguishes it from the sibling tool meta_send_conversion_event by indicating it's for testing.

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 explicitly tells when to use this tool (for testing CAPI setup) and references the alternative: 'Same args as meta_send_conversion_event but auto-sets a test_event_code if not provided. Use the test_event_code from Events Manager > Test Events tab.' This guides the agent to choose the right tool.

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