Skip to main content
Glama

Посещения по источникам, устройствам, браузерам и странам

get_quiz_visit_segments
Read-onlyIdempotent

Разбивает посещения опроса (каждое открытие опроса) по одному признаку: значению параметра ссылки (utm_source, utm_campaign или любая скрытая переменная), устройству, браузеру или стране. По каждому значению: открытия, уникальные браузеры, посещения хотя бы с одним ответом и посещения с завершённым ответом. Строка со значением null — посещения без этого параметра (by=param) или с неизвестным устройством, браузером, страной; у by=param пустая строка "" — отдельная строка: параметр был, но пустой. Строки — по числу открытий, null последней, не больше 200; truncated = true — строк было больше. Имена параметров, встречавшиеся в завершённых ответах, — в filters.extra_fields у get_quiz_report (на тарифе с фильтрами результатов), объявленные переменные ссылки — в get_quiz_variables на любом тарифе (quiz://{id}/hidden_options — другое, их там нет). В опросе с анонимными ответами разбивка по устройству, браузеру и стране пустая.

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>",
      "by": "<by>"
    },
    "name": "get_quiz_visit_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYesПо какому признаку разбить: param (параметр ссылки, нужен key), device, browser, country.
keyNoИмя параметра ссылки при by=param, например utm_source.
deviceNoТолько посещения с этого устройства: desktop, mobile, tablet.
date_toNoПоследний день периода, YYYY-MM-DD, включительно.
quiz_idYesID опроса.
date_fromNoПервый день периода, YYYY-MM-DD, включительно. Период — по дню посещения в часовом поясе владельца опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnly/idempotent annotations, the description discloses return behavior: per-segment opens, unique browsers, answered and completed visits, null vs empty-string rows, ordering and 200-row truncation. It also warns that device/browser/country breakdowns are empty for anonymous-answer quizzes. No annotations are contradicted.

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?

It is front-loaded with purpose and metrics, then null semantics, ordering limits, source-of-parameter-names, and anonymous caveat, with little filler. The single dense paragraph is information-rich but could be more scannable, so not a full 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry return-value semantics; it does so with metric names, row ordering/truncation, null and empty-string handling, and the anonymous-quiz limitation. Together with annotations and the complete input schema, an agent has enough to call and interpret this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for `by=param` (any hidden variable, null row for missing, separate empty-string row) and unknown values for device/browser/country. It does not add much for date_from/date_to or the device filter parameter, keeping it below 5.

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?

The first sentence gives a precise verb ('Splits') and resource ('quiz visits / each opening') and names the four segmentation modes, so an agent knows exactly what the tool returns. It also flags related lookups (get_quiz_report, get_quiz_variables) and that hidden_options is not the source, which reduces sibling confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is clearly implied: choose one segmentation attribute via `by`, and the description supplies parameter-source guidance and an anonymous-answer caveat. However, it does not explicitly say when to choose this over get_quiz_visits (total visits) or another sibling, so it is clear context rather than full when/when-not guidance.

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