Skip to main content
Glama

Отправка в Zapier

manage_quiz_zapier
Destructive

Интеграция опроса с Zapier. Со стороны опроса это один переключатель: включена отправка ответов или нет. Сами связки собираются на стороне Zapier, ключей здесь вводить не нужно. Удаление снимает и подписки — связка в Zapier перестанет получать ответы, и собирать её придётся заново там же.

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>",
      "action": "<action>"
    },
    "name": "manage_quiz_zapier"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: show — состояние и число связок, activate — включить, deactivate — выключить, delete — убрать интеграцию вместе с подписками.
quiz_idYesID опроса.

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 and non-idempotent, but the description adds the crucial consequence the annotations can't convey: delete also removes the Zapier subscriptions, so the automation stops receiving answers and must be rebuilt in Zapier. It also clarifies that nothing has to be configured locally. It stops short of covering deactivate/activate semantics (e.g. whether re-enabling restores prior subscriptions).

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?

Three tight sentences: what it is, how it works locally, then the destructive consequence last. Every sentence carries information and nothing is front-loaded with filler, though the middle sentence about Zapier-side assembly overlaps slightly with the earlier framing.

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?

For a two-parameter mutation tool with no output schema, the agent gets the integration model, the effect of deletion, and confirmation that no credentials are needed here. The `show` return value is only documented inside the enum rather than the description, a minor gap but a covered one.

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 the action enum already spells out all four modes including what show returns and what delete removes. The description adds only general framing ('one switch', no keys needed) rather than new per-parameter detail, so the schema is doing the semantic work.

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 identifies a specific resource (the quiz's Zapier integration) and frames its scope as a single on/off switch for answer delivery, plus removal. That is clear enough to act on, but it draws no boundary against related outbound-integration siblings such as create_quiz_webhook or manage_quiz_google_sheets, so the agent must guess which one applies.

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?

Usage is only implied: the description says the quiz side is 'one switch' and that no keys are entered here, which hints at configuration boundaries. It never states when to choose this tool over another integration tool, nor any prerequisites (plan, permissions, whether the quiz must be published first).

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