get_pixelOne pixel, including the HTML snippet to paste on its site.
| Name | Required | Description | Default |
|---|---|---|---|
| pixel_id | Yes | pixel_id returned by create_pixel or list_pixels, never an account_id. Example: px_7a1b2c3d4e5f6a7b |
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | ||
| snippet | No | ||
| pixel_id | Yes | ||
| data_kind | Yes | ||
| checked_at | No | ||
| check_error | No | ||
| install_status | Yes | ||
| consent_enabled | No | ||
| evaluation_mode | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / pixel_id / descriptionPrevious value: -"Exact pixel_id returned by create_pixel or list_pixels; never an account ID"New value: +"pixel_id returned by create_pixel or list_pixels, never an account_id. Example: px_7a1b2c3d4e5f6a7b"Input schema / additionalPropertiesAdded value: +falseInput schema / properties / pixel_id / descriptionAdded value: +"Exact pixel_id returned by create_pixel or list_pixels; never an account ID"Input schema / properties / pixel_id / maxLengthAdded value: +80Input schema / properties / pixel_id / minLengthAdded value: +1Input schema / properties / pixel_id / patternAdded value: +"^[A-Za-z0-9_-]+$"Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "check_error": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Check Error"
+ },
+ "checked_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Checked At"
+ },
+ "consent_enabled": {
+ "anyOf": [
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Consent Enabled"
+ },
+ "data_kind": {
+ "enum": [
+ "synthetic",
+ "resolved"
+ ],
+ "title": "Data Kind",
+ "type": "string"
+ },
+ "domain": {
+ "title": "Domain",
+ "type": "string"
+ },
+ "evaluation_mode": {
+ "title": "Evaluation Mode",
+ "type": "boolean"
+ },
+ "install_status": {
+ "enum": [
+ "not_checked",
+ "installed",
+ "not_installed",
+ "unreachable"
+ ],
+ "title": "Install Status",
+ "type": "string"
+ },
+ "pixel_id": {
+ "title": "Pixel Id",
+ "type": "string"
+ },
+ "snippet": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Snippet"
+ }
+ },
+ "required": [
+ "pixel_id",
+ "domain",
+ "install_status",
+ "evaluation_mode",
+ "data_kind"
+ ],
+ "title": "Pixel",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact — that the payload includes the HTML snippet needed to install the tag — but says nothing about scoping, permissions, or error cases.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short clause with zero filler, and the most important fact (the install snippet) is front-loaded. It is efficient, though the terseness edges toward under-specification rather than pure conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value detail is not required, and annotations cover the safety contract. What is missing is the routing information an agent needs to choose this tool over list_pixels or create_pixel, which leaves the definition only minimally complete for its sibling set.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the pixel_id param is already richly documented in the schema ('returned by create_pixel or list_pixels, never an account_id', plus an example). The description contributes no additional meaning about the parameter, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is a noun fragment ('One pixel, including the HTML snippet...') rather than a verb+resource statement; the action of reading is only implied. The title supplies 'Read pixel and install tag', and the singular 'one pixel' loosely distinguishes it from list_pixels, but the description text itself does not state a clear verb.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance and no mention of alternatives such as list_pixels (for enumerating) or create_pixel (for provisioning). The agent must infer the retrieval context purely from the name and the schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.