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

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

revoke_chat_invite_link

Revoke an invite link to prevent new members from joining via that link. Specify the invite link and optionally the chat ID.

Instructions

Revoke an invite link 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": {
      "invite_link": "<invite_link>"
    },
    "name": "revoke_chat_invite_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoChat ID or @channel_username. Optional — defaults to log group
invite_linkYesThe invite link to revoke

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only states that it revokes an invite link, but fails to mention side effects, permission requirements, or consequences. Crucial context is missing.

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 extremely concise: one sentence, 12 words. It front-loads the action and is free of unnecessary information.

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 lack of output schema and annotations, the description is insufficient. It does not explain return values, error conditions, or what happens after revocation. For a state-changing tool, more context is needed.

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%, and the description adds no new meaning beyond what the schema's descriptions already provide. Both parameters are clearly defined in the schema, so the description offers no additional value.

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 ('Revoke') and the resource ('invite link'), and adds context about default behavior when chat_id is omitted. This distinguishes it from sibling tools like edit_chat_invite_link or create_chat_invite_link.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It only states a default behavior, which is insufficient.

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