Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Изменить отправленное сообщение

dialogs_edit_message

Edit the text of a message already sent by a bot or operator, updating it for the recipient and in the panel. Only your own messages; buttons stay unchanged.

Instructions

Меняет текст сообщения, которое бот или оператор уже отправили, — и у собеседника, и в переписке панели. Только свои сообщения: чужие и служебные не правятся. Не дошедшее изменить нельзя — только отправить заново; подпись к вложению панель пока не правит. Кнопки остаются прежними. Бот должен быть запущен; слишком старое сообщение платформа может не дать изменить.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
textYesНовый текст целиком.
dialogYesДиалог: имя собеседника, @username, номер чата или идентификатор.
messageYesid сообщения из dialogs_history.
parse_modeNoРазметка: HTML или пустая строка для обычного текста.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / message / format
      Added value: +"uuid"
    • addedInput schema / properties / message / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / parse_mode
      Added value: +{
+  "description": "Разметка: HTML или пустая строка для обычного текста.",
+  "enum": [
+    "",
+    "HTML"
+  ],
+  "type": "string"
+}
  2. Addedv0.1.16

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-destructive, open-world, non-idempotent behavior; the description adds substantial context beyond that: the bot must be running, very old messages may be rejected by the platform, buttons stay unchanged after the edit, and undelivered messages cannot be edited at all. Auth scopes and rate limits remain unmentioned, so it is not exhaustive.

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?

Front-loaded with the core action, then a compact set of constraints in short sentences with no filler. The constraint list is slightly dense but each clause carries a distinct caveat an agent needs.

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 5-parameter mutation tool with no output schema and full schema coverage, the description supplies the important behavioral envelope: ownership restriction, editability window, and button preservation. Return payload semantics are not described, which is a minor gap given no output schema exists.

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%, so all five parameters are already documented (dialog formats, case fallback, message id from dialogs_history, parse_mode enum). The description adds only that the entire text is replaced, not new per-parameter syntax, so the baseline of 3 applies.

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?

States a specific verb and resource ('меняет текст сообщения') plus the exact scope: messages already sent by the bot or operator, visible both to the counterpart and in the panel. An agent can distinguish this from dialogs_delete_message or dialogs_reply without opening the schema.

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?

Gives explicit when-not conditions: only your own messages (foreign and service messages are not editable), undelivered messages must be re-sent instead, and attachment captions are not supported. It does not name a sibling tool (e.g. delete message) as the alternative action, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools