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

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

export_chat_invite_link

Export the primary invite link for a Telegram chat. Specify a chat ID or username, or leave blank to use the default log group.

Instructions

Export the primary invite link for a chat. If chat_id is omitted, targets the default log group.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_chat_invite_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoChat ID or @channel_username. Optional — defaults to log group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. 'Export' implies retrieval, but does not disclose whether it modifies state, required permissions, error conditions, or rate limits. Insufficient for a tool with no annotations.

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?

Two sentences, no filler. Front-loaded with verb and resource. Every word earns its place.

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 simple one-parameter tool with no output schema, the description covers the essential purpose and default behavior. Lacks details on return value, but acceptable given simplicity.

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 covers 100% of parameters, and the description 'If chat_id is omitted, targets the default log group' duplicates schema info. No additional meaning beyond schema for the single parameter.

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?

Clearly states the verb 'Export' and resource 'primary invite link for a chat'. Implicitly distinguishes from sibling tools like 'create_chat_invite_link' by specifying 'primary', but does not explicitly differentiate from alternatives.

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

Usage Guidelines3/5

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

Provides context for when to use (export primary invite link) and default behavior when chat_id omitted. However, no guidance on when not to use or comparison with sibling tools like create or edit invite links.

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