Skip to main content
Glama
AdvisorPPC X Ads MCP Server

AdvisorPPC X Ads MCP Server

Delete X Pixel

x_ads_delete_pixel
Destructive

Delete a web event tag to stop conversion tracking for that event. Requires explicit confirmation before removal.

Instructions

Delete a web event tag. Conversion tracking for that event stops. confirm=true after the user named it.

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": {
      "account_id": "<account_id>",
      "web_event_tag_id": "<web_event_tag_id>"
    },
    "name": "x_ads_delete_pixel"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
account_idYesAds API account id from x_ads_list_accounts, e.g. 18ce55v2od2
web_event_tag_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds meaningful behavioral detail beyond the destructiveHint annotation: deleting the tag stops conversion tracking and requires the confirm flag to be set only after the user names the tag. This gives the agent a concrete workflow expectation that annotations alone do not supply.

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 two short sentences with no filler. The primary action, consequence, and confirmation requirement are all front-loaded and easy to parse.

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 simple three-parameter destructive operation, the description covers the key behavioral context: what is deleted, what changes afterward, and when confirm should be true. No output schema is provided, but return-value details are less critical for a delete operation.

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 only 33%, so the description must compensate for underdocumented parameters. It does clarify the confirm parameter's intended usage, and account_id is already described in the schema, but web_event_tag_id receives no additional semantic explanation beyond its name.

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 identifies the operation as deleting a web event tag and states the business consequence (conversion tracking stops). It does not explicitly distinguish itself from sibling create/update pixel tools, but the verb and resource are unambiguous.

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?

The confirmation condition 'confirm=true after the user named it' provides useful pre-call guidance, and the effect of stopping conversion tracking implies a destructive context. However, it does not explicitly say when to choose this tool over list/update/create pixel alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.