Skip to main content
Glama

Собрать новую воронку черновиком

create_funnel_draft

Новая воронка бота черновиком. Людям ничего не уходит: опубликовать её может только человек в кабинете, ссылка в ответе (editor_url). Формат воронки: get_funnel_format. В ответе проверка (errors, warnings): исправьте ошибки правкой черновика.

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": {
      "bot_id": "<bot_id>",
      "name": "<name>",
      "graph": "<graph>"
    },
    "name": "create_funnel_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
graphYes
bot_idYes
Idempotency-KeyNoКлюч повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / Idempotency-Key
      Added value: +{
      +  "description": "Ключ повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds real value by disclosing the side-effect boundary (no messages go out to people) and the response contents (editor_url, errors, warnings). It does not address the idempotency behavior, which is notable given idempotentHint=false while the schema's Idempotency-Key promises duplicate calls return the first response.

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 short sentences, front-loaded with what is created and the safety-relevant fact that nothing is dispatched. The telegraphic style is dense but every sentence carries operational information; no filler.

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 correctly compensates by naming the returned fields (editor_url, errors, warnings) and telling the agent to fix errors via draft edits rather than re-creating. The remaining gap is parameter-level detail for a nested graph payload, partially covered by the format-tool reference.

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 only 25% — only Idempotency-Key is documented, while bot_id, name, and the nested free-form graph object are bare. The pointer 'Формат воронки: get_funnel_format' meaningfully compensates for the graph structure, but bot_id and name semantics remain undocumented in both places.

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 states a specific verb and resource ('Новая воронка бота черновиком') and makes the key qualifier explicit — the funnel is created as a draft, not published. It does not explicitly contrast itself with update_funnel_draft, so an agent must infer the create-vs-edit boundary, but the core action is unambiguous.

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 operating context: nothing is sent to end users, only a human in the dashboard can publish, and the funnel body must follow get_funnel_format. That routes the agent to the correct companion tool before calling. It stops short of stating when to choose this over update_funnel_draft or check_funnel.

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