telegram-bot-mcp

set_chat_title

Update a chat's title. Provide a new title (1-128 characters) and optionally a chat ID or @channel_username; defaults to the configured log group.

Instructions

Set a new title for a chat. If chat_id is omitted, targets the default log group.

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": {
      "title": "<title>"
    },
    "name": "set_chat_title"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	New chat title (1-128 characters)
`chat_id`	No	Chat ID or @channel_username. Optional — defaults to log group

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.3Mar 5, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the action and default targeting, omitting important details like whether the tool is idempotent, if it returns a confirmation, or if special permissions are required. This is insufficient for an agent to understand side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loading the core action. Every sentence adds necessary context without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and only two parameters, the description covers the basic functionality. However, it lacks behavioral details (e.g., whether the operation succeeds silently, error conditions) that would be expected for a mutation tool with no annotations. It is minimally complete but not thorough.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the default behavior of chat_id, but does not add semantic information for the title parameter beyond what the schema already provides (length constraints). Thus, minimal additional contribution.

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 tool's action ('Set a new title for a chat') and distinguishes it from sibling tools that modify other chat properties (e.g., set_chat_description, set_chat_photo). The mention of default behavior when chat_id is omitted adds specificity.

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 tells when to use the tool (to set a chat title) and provides context about default targeting. However, it does not explicitly mention when not to use it or suggest alternatives among the many sibling tools, which would improve guidance.

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

Deploy Server