Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

pixels_get

Retrieve detailed diagnostics and status for a single Meta pixel using its ID. Provides the data needed to troubleshoot and optimize pixel performance.

Instructions

Get detailed info about a single pixel including diagnostics.

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": {
      "pixel_id": "<pixel_id>"
    },
    "name": "pixels_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pixel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only mentions 'including diagnostics' without explaining what diagnostics entails, return format, or any safety considerations. This is a significant gap for a tool with zero annotation coverage.

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 a single sentence of nine words, front-loaded with the action and resource. It is concise with no redundant or irrelevant content.

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

Completeness2/5

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

Given the lack of annotations, output schema, and parameter descriptions, the description is too sparse. It doesn't specify what detailed info is returned, how diagnostics are structured, or any potential error conditions. A one-line description for a getter with no other metadata is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter (pixel_id) with 0% description coverage, and the description does not explicitly explain the parameter's meaning or format beyond the name. It only implies that pixel_id identifies the pixel, adding minimal value over the schema.

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 clearly states 'Get detailed info about a single pixel', using a specific verb and resource. It distinguishes from siblings like pixels_list by emphasizing 'single pixel', though it doesn't explicitly name alternatives.

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

Usage Guidelines3/5

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

Usage is implied: use when you need information about one specific pixel, as opposed to pixels_list or pixels_get_stats. However, there is no explicit mention of when not to use it or reference to alternative tools.

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