Skip to main content
Glama
Anonymouse8882

Telegram MCP

click_inline_button

Click an inline callback button on a Telegram message by providing chat, message ID, and button identifier (data, data_hex, or text). Returns the button's response popup, alert, url, or cache_time.

Instructions

点击某条消息附带的 inline 按钮(callback 类型)。

定位按钮的三种方式,至少提供一个:

  • data: 按钮的 callback data(UTF-8 字符串,最常见,如 "confirm:42");

  • data_hex: callback data 的十六进制字节串,用于二进制数据;

  • text: 按钮显示的文字(同一消息里必须唯一)。

Args: chat: 消息所在对话。 message_id: 带 inline 按钮的消息 ID。 data: 按钮 callback data 的 UTF-8 文本。 data_hex: 按钮 callback data 的十六进制表示。 text: 按钮显示的文字。

Returns: bot 返回的响应:message(弹窗文字)、alert(True 为强制 alert)、 url(有则为跳转链接)、cache_time(客户端缓存秒数)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatYes
dataNo
textNo
data_hexNo
message_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It explains the return value and that the tool triggers a callback button, but it does not mention potential side effects (e.g., button becoming disabled, permission requirements, or error conditions). This is a moderate gap.

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 description is well-structured with a summary, locator methods list, Args section, and Returns section. It is slightly verbose with repetition of parameter names, but overall efficient and front-loaded.

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 tool with 5 parameters and no output schema, the description covers all key aspects: identification methods, required fields, and return object. It lacks error handling details but is sufficient for basic usage. Minor gaps in edge-case guidance.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description fully compensates by explaining each parameter with examples (e.g., data: 'confirm:42', data_hex for binary). The three locator methods and their constraints are clearly defined, adding significant value beyond the raw schema.

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 description clearly states the action ('click') and the resource ('inline button on a message'), and distinguishes it from sibling tools like press_reply_keyboard. The three locator methods are explicitly listed, leaving no ambiguity.

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?

The description specifies when to use the tool (to click callback inline buttons) and provides conditions for parameter usage (at least one of data/data_hex/text). However, it does not explicitly state when not to use it or compare with alternatives, which would enhance clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Anonymouse8882/TelegamMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server