Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_pixel_health

Read-only

Audit Snapchat pixel signal readiness and return prioritized event-quality recommendations to fix tracking issues; read-only and defaults to SNAP_PIXEL_ID.

Instructions

Pixel signal readiness and event-quality recommendations, highest priority first (read-only). Pixel defaults to SNAP_PIXEL_ID.

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": "snap_pixel_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
pixel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the parenthetical '(read-only)' is largely redundant, though it does not contradict them. The description adds two genuinely useful behavioral facts: results are ordered highest-priority-first, and the pixel defaults to SNAP_PIXEL_ID. It does not disclose what a recommendation looks like, whether results can be empty, or what 'signal readiness' is measured against.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and ordering, with no filler. The '(read-only)' parenthetical is the only wasted token since annotations already state it.

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?

With no output schema, the description must characterize the return value, and it only vaguely does so ('recommendations, highest priority first'). For a diagnostic tool an agent would benefit from knowing the shape of a recommendation (severity, affected event, suggested action) and whether an empty result means healthy or unknown.

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 one parameter at 0% schema description coverage, so the description carries the burden, and it does supply the default value (SNAP_PIXEL_ID), which the schema does not encode. However, it says nothing about the expected format despite a strict pattern constraint, nor what happens when the pixel is invalid or inaccessible.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource domain (pixel signal readiness and event-quality recommendations) and states the ordering of results, so an agent can tell it is a pixel-level diagnostics/recommendation tool. It lacks an explicit verb ('get'/'report') and does not distinguish itself from sibling diagnostics such as snap_health_check, snap_capi_status, or snap_anomaly_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus the many other health/diagnostic siblings (snap_health_check, snap_audience_health, snap_capi_status, snap_anomaly_check). The only usage-adjacent information is the implied read-only nature and the default pixel, neither of which tells an agent when this tool is the right choice.

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