Skip to main content
Glama

Reenviar eventos CAPI

pixel_push_capi
DestructiveIdempotent

Enfileira (ou reenfileira) os eventos Purchase/Refund elegíveis ao Meta CAPI da org. O dedup por event_id=conversionId garante idempotência (reenvio não duplica). DRY-RUN com dry_run:true. Requer plano Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pixel_push_capi"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNotrue ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 explains the idempotency mechanism (dedup by event_id=conversionId, so resend does not duplicate), names the event types affected, and adds a Pro-plan prerequisite. It does not fully restate that execution sends real events externally or clarify irreversibility/billing impact, but annotations already carry the destructive/open-world safety profile.

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 short, front-loaded, and every sentence adds value: purpose, idempotency guarantee, dry-run note, and plan requirement. There is no wasted text.

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 one-parameter, annotation-rich tool with no output schema, the description covers the core call requirements: event scope, idempotency, dry-run default, and Pro-plan gating. It could mention how to verify eligibility or check CAPI status afterward, but it 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?

There is only one parameter and schema description coverage is 100%, so the schema already fully explains dry_run true versus false. The description adds only a reminder that dry_run:true triggers DRY-RUN, which is useful but not meaningfully beyond the schema.

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 verb and resource: enqueue/re-enqueue eligible Purchase/Refund events to the organization's Meta CAPI. It is clearly distinguishable from siblings like get_capi_status or send_test_event because it describes actual event re-sending, not status retrieval or test events.

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: this is for eligible Purchase/Refund events, supports dry-run via dry_run:true, and requires a Pro plan. It does not explicitly name alternatives such as send_test_event or trigger_sync, nor does it state when not to use this tool, so it stops short of full when/when-not guidance.

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