Skip to main content
Glama
Sign In
telegram-bot-mcp

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

edit_chat_subscription_invite_link

Edit a subscription invite link's name to keep it organized. Update invite links for Telegram channels or groups without recreating them.

Instructions

Edit a subscription invite link.

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": {
      "invite_link": "<invite_link>"
    },
    "name": "edit_chat_subscription_invite_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew invite link name (up to 32 chars)
chat_idNoChat ID or @channel_username. Optional — defaults to log group
invite_linkYesThe invite link to edit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'Edit,' implying mutation, but does not disclose effects (e.g., whether previous settings are overwritten, if permissions required, or side effects). No behavioral context is provided.

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 a single sentence of 5 words, highly concise with no fluff. However, it is perhaps too minimal, but for conciseness it earns a high score.

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

Completeness2/5

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

Given the tool has 3 parameters, no output schema, and no annotations, the description leaves out critical context such as return values, side effects, and when to use it. It is insufficient for an agent to fully understand the tool's behavior.

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 baseline is 3. The description adds no extra meaning beyond the schema; it does not explain parameter usage or constraints beyond what the schema already provides.

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 clearly states 'Edit a subscription invite link,' specifying both the action and resource. It distinguishes from the sibling tool 'edit_chat_invite_link' by including 'subscription,' though it does not elaborate on which properties can be edited.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'create_chat_subscription_invite_link' or 'revoke_chat_invite_link'. There is no mention of conditions, prerequisites, or exclusions.

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