Skip to main content
Glama

Listar links rastreados

pixel_get_links
Read-only

Lista os links rastreados da conta com o PRODUTO detectado de cada um. Por link: apelido (label), URL (https://…/r/{slug}), modo (edge=rastreado | static=estático), campanha/adset/ad associados, cliques (total + último) e o produto da Shopee (nome, imagem, preço em centavos, comissão em basis points, disponibilidade e quando foi checado). Filtros por status e campanha; paginação total/count/offset/has_more/next_offset.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo de links (1–100, default 50).
offsetNoDeslocamento para paginação (default 0).
statusNoFiltro de status (default all).
campaign_idNoFiltra os links de uma campanha (metaCampaignId, modo estático). Opcional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real value: it tells the agent that each record carries the detected Shopee product, that mode distinguishes edge (tracked) from static links, and that pagination returns total/count/offset/has_more/next_offset — none of which the annotations convey.

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?

Purpose is front-loaded in the first clause, followed by a compact per-field inventory and then filters/pagination in a predictable order. The single dense paragraph and the parenthetical field-style listing are efficient, though the middle sentence is heavy enough to be harder to scan than it needs to be.

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?

With no output schema, the description must describe what comes back, and it does so thoroughly: label, URL with the /r/{slug} template, mode, campaign/adset/ad attribution, click counts, and full product payload including price units (cents), commission units (basis points), availability, and last-checked. Missing only ordering/default result behavior, which is minor for a read-only list.

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 all four parameters (limit, offset, status, campaign_id) are documented in the schema, including limits and defaults. The description adds only a restatement of the status and campaign filters; the mention of 'modo estático' duplicates what campaign_id's schema description already says. Baseline 3 is correct.

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?

Opens with a specific verb and resource: 'Lista os links rastreados da conta' plus the distinctive 'com o PRODUTO detectado de cada um', which signals a capability beyond a plain link listing. It never names a sibling tool or draws an explicit boundary, so sibling differentiation is left implicit.

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?

Enumeration of the available filters ('Filtros por status e campanha') and pagination implies the intended usage, but there is no statement of when to reach for this versus pixel_get_campaigns or pixel_get_products_sold, nor any exclusion or precondition.

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