Skip to main content
Glama

Sincronizar agora

pixel_trigger_sync
Idempotent

Enfileira o pipeline de sincronização (pull Shopee → match → produto → insights Meta → push CAPI → agregação), o mesmo do "Sincronizar agora" do painel. ASSÍNCRONO: responde imediatamente e a cadeia roda em ~1–2 min; consulte pixel_get_dashboard_summary depois. Liberado a partir do plano Starter.

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_trigger_sync"
  }
}

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?

Annotations already declare non-read-only, idempotent, non-destructive, open-world. The description adds genuinely new behavioral facts: asynchronous enqueue semantics, an expected completion window of ~1–2 min, the full downstream side-effect chain, and a subscription-plan requirement that no annotation captures. It does not cover failure modes, duplicate-run behavior, or what the immediate response contains, so it is strong but not exhaustive.

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?

Three tightly packed sentences: what it enqueues, how it behaves (async + latency + follow-up), and the eligibility constraint. The most decision-relevant fact (ASÍNCRONO) is emphasized mid-text and nothing is redundant with the schema.

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, no-output-schema enqueue tool this is nearly complete: side effects, timing, follow-up tool, and plan gate are all present. The only gap is that the immediate return payload (e.g. a job identifier for polling) is not hinted at, which matters slightly more given there is no output schema.

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 description coverage is 100% and the single dry_run parameter is thoroughly documented in the schema itself (default true, only send false after user confirmation). The description adds nothing about the parameter, so the baseline 3 applies — the schema does all the work here.

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?

States a specific verb ("Enfileira o pipeline de sincronização") plus the exact resource and its internal chain (pull Shopee → match → produto → insights Meta → push CAPI → agregação). It also anchors the tool to a known UI action ("o mesmo do 'Sincronizar agora' do painel"), making it instantly distinguishable from read-only siblings like pixel_get_shopee_sales or pixel_push_capi.

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?

Gives clear operating context: it is asynchronous, runs ~1–2 min, and the agent should consult pixel_get_dashboard_summary afterwards. It also states plan gating (Starter+). It stops short of explicitly naming when NOT to use it (e.g. single-event push via pixel_push_capi) or what to do if a sync is already running, so it falls just short of a full when/when-not/alternatives treatment.

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