Skip to main content
Glama

Счётчики и пиксели

manage_quiz_analytics
Destructive

Счётчики и пиксели опроса: Google Аналитика, Яндекс.Метрика, пиксель VK, пиксель Facebook. Показывает состояние, задаёт номер счётчика, включает, выключает и убирает интеграцию. Номер счётчика не секрет — он виден в коде любой страницы, — поэтому ничего чужого вводить не приходится. Значение пишется и в интеграцию, и в версию опроса, откуда его читает рендер.

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": {
      "quiz_id": "<quiz_id>",
      "service": "<service>",
      "action": "<action>"
    },
    "name": "manage_quiz_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: show — состояние, save — задать номер, activate — включить, deactivate — выключить, delete — убрать.
counterNoНомер счётчика или id пикселя, до 20 символов. Пустое значение стирает номер.
quiz_idYesID опроса.
serviceYesКакой счётчик: google — Google Аналитика, yandex — Яндекс.Метрика, vk — пиксель VK, fb — пиксель Facebook.
versionNoТолько для google: ga4 или ua.
is_webvisorNoТолько для yandex: включить вебвизор — запись действий посетителя.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety bar is partly covered. The description adds genuinely useful context beyond that: the counter number is non-secret page-visible data, and the saved value is written both to the integration record and to the quiz version that the renderer reads. It does not state whether 'delete' is irreversible or what permissions are needed.

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 compact sentences, front-loaded with the supported services and the action set, followed by the reassurance about the counter number and the data-propagation note. Slightly dense but free of padding.

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 six parameters, three enums, no output schema and annotations covering the destructive profile, the definition supplies what an agent needs to pick the tool and construct a call. The remaining gap is that 'show' is not described in terms of what state information comes back, but that is minor given the tool's scope.

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%, including enum explanations for action, service and version, so the schema already carries parameter meaning and the baseline of 3 applies. The description's only real addition is that the stored counter value propagates into the quiz version consumed by rendering; it adds nothing about 'version', 'is_webvisor' or empty-value clearing.

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 names a concrete resource (quiz counters/pixels: Google Analytics, Yandex.Metrika, VK pixel, Facebook pixel) and a concrete set of verbs (show state, set counter number, enable, disable, remove). It is immediately clear this manages analytics integrations rather than CRM, messenger or payment settings, though it does not explicitly contrast itself with those siblings.

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 five actions are enumerated in prose, which implies when each applies, but that mapping largely duplicates the 'action' enum descriptions. There is no explicit statement of prerequisites (e.g. that activate requires a saved counter number) or of when to choose this tool over adjacent integration managers; usage is implied rather than stated.

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