Skip to main content
Glama

Заказанные респонденты

get_respondent_campaigns
Read-onlyIdempotent

Заказанные респонденты: кампании закупки прохождений и их результат. Без campaign_id — список кампаний аккаунта с ценой одного ответа и минимальным размером группы. С campaign_id — карточка кампании: статус и модерация, просмотры, ответы, конверсия, первое и последнее прохождение, среднее время, социально-демографические параметры заказа (названия городов уже подставлены) и данные об оплате. Только чтение: заказать кампанию и оплатить её через ассистента нельзя, это списание денег. Расчёт доступной аудитории по соцдему тоже делают в кабинете.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_respondent_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idNoID кампании из списка. Без него приходит список кампаний.
workspace_idYesID аккаунта из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still earns credit by explaining the reason for the read-only limit (ordering a campaign is a real money charge) and by flagging that city names are pre-resolved and that audience estimation is out of scope.

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?

The lead sentence states the resource and the two modes are then separated cleanly, with the read-only constraint and the cabinet-only operations placed last where they are cheapest to skip. The enumeration of card fields is dense but each item tells the agent what data is available.

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?

There is no output schema, so the description carries the full burden of describing returns, and it does so for both the list (price per response, minimum group size) and the card (status, moderation, views, answers, conversion, timings, demographics, payment). Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 both parameters are already documented, making 3 the baseline. The description adds meaning beyond the schema by explaining what each campaign_id mode returns and by noting the pre-substituted city names in the demographics payload.

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 specific resource and verb: purchased respondent campaigns and their results, with an explicit split between the list view and the single-campaign card. It never names a sibling tool to contrast with, so an agent must infer the boundary from the subject matter alone, which keeps it just short of a 5.

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?

It gives clear mode selection: omit campaign_id to get the account's campaign list, supply it to get the campaign card. It also states exclusions — ordering or paying for a campaign, and calculating reachable audience by socio-demographics, must be done in the cabinet — though it does not point to any alternative MCP tool.

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