Skip to main content
Glama

Evento de teste no pixel

pixel_send_test_event

Dispara um evento de teste ao Meta CAPI usando test_event_code (aparece em Test Events do Gerenciador de Eventos; NÃO afeta produção/otimização). Útil para validar a integração do Pixel/CAPI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "test_event_code": "<test_event_code>"
    },
    "name": "pixel_send_test_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_nameNoEvento a simular (default Purchase).
value_centsNoValor (comissão) em CENTAVOS de BRL. Opcional.
test_event_codeYesCódigo de teste do Gerenciador de Eventos (TESTxxxxx).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / value_cents / minimum
      Added value: +0
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description adds substantive behavior: the event appears in Test Events and does not affect production or optimization. That is important context the annotations do not convey, though return behavior and any auth/rate-limit constraints remain unstated.

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?

Two compact sentences with the core action, safety scope, and validation use case front-loaded. The parenthetical is informative rather than redundant, and there is no filler.

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 three-parameter test-event tool with full schema coverage and annotations, the description covers purpose, scope, and validation use sufficiently. It could mention the expected result or confirmation behavior, but the description is largely complete for correct invocation.

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 the parameters are already documented. The description clarifies that test_event_code is the Test Events code and implies its role, but it does not add meaning for event_name or value_cents beyond what the schema provides.

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 states a specific action (fires a test event) against a specific target (Meta CAPI) and scopes it clearly as non-production. This distinguishes it from production event-pushing siblings such as pixel_push_capi without needing to name them.

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?

It gives clear usage context: useful for validating the Pixel/CAPI integration and routed through Test Events in Gerenciador de Eventos. It stops short of explicitly naming an alternative for production sends or stating when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources