Skip to main content
Glama

Editar url_tags do anúncio

pixel_edit_campaign_url
DestructiveIdempotent

Atualiza os url_tags de um anúncio (ad) Meta — por exemplo para colocar os parâmetros do link rastreado. NÃO gera o link (isso é só no painel): recebe os url_tags prontos. DRY-RUN com dry_run:true. Requer plano Pro.

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": {
      "ad_id": "<ad_id>",
      "url_tags": "<url_tags>"
    },
    "name": "pixel_edit_campaign_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYesID externo do anúncio (ad) Meta.
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.
url_tagsYesNovos url_tags (query string de macros).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url_tags / maxLength
      Added value: +4096
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=true, but the description adds two things annotations cannot convey: the Pro-plan gate and that dry_run is the default safe mode. It stops short of saying the write overwrites existing url_tags or what a rejection looks like.

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?

Four short clauses, front-loaded with the action and immediately followed by the scope boundary and safety default. Slightly telegraphic phrasing ('DRY-RUN com dry_run:true.') but nothing wasteful.

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?

A destructive single-target mutation whose safety profile is fully covered by annotations, whose three parameters are fully schema-documented, and whose plan requirement and dry-run default are disclosed in the description. Only the overwrite/irreversibility of existing tags is left implicit.

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 already documents ad_id, url_tags (query string of macros) and dry_run (default true, only send false after user confirmation). The description's 'recebe os url_tags prontos' adds only a light format precondition, so the 3 baseline applies.

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 and resource ('Atualiza os url_tags de um anúncio (ad) Meta') and explicitly bounds the scope by denying an adjacent capability ('NÃO gera o link... recebe os url_tags prontos'). No sibling tool deals with url_tags, so the agent can route to it unambiguously.

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?

Gives the precondition that a Pro plan is required and implies the tool is for pushing prepared url_tags onto an ad, but offers no explicit when-to-use-vs-alternative guidance and no exclusions. The dry-run note is operational guidance rather than usage routing.

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