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

telegram-mcp-server

by KYONY
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

telegram_api_login

Authenticate with Telegram API credentials to enable scraping of channels and groups for data collection.

Instructions

Login to Telegram using API credentials for fast, efficient scraping

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": "telegram_api_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_idNoYour Telegram API ID (get from https://my.telegram.org)
api_hashNoYour Telegram API Hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations, the description carries full burden for disclosing behavior. It only says 'Login' and 'fast, efficient scraping', providing no information about session persistence, authentication checks, rate limits, error handling, or the effect of repeated logins. The tool's behavior is entirely opaque.

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, front-loaded sentence that clearly states the action. It is concise, though the phrase 'fast, efficient scraping' adds a subjective flourish without functional value.

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?

As a login tool with no output schema and no annotations, the description fails to explain what happens on success/failure, what the returned data looks like, or why both parameters are optional. It is incomplete for an agent to confidently invoke and interpret the result.

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%, with both api_id and api_hash having descriptions. The tool description itself adds nothing beyond the schema, so the baseline of 3 is appropriate.

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 the tool logs into Telegram using API credentials, which is a specific verb+resource action. It distinguishes somewhat from sibling tools like telegram_login by emphasizing 'API credentials', but doesn't fully disambiguate between the two login-related tools.

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 telegram_login or other authentication tools. The phrase 'for scraping' implies a use case, but there is no explicit when-to-use or when-not-to-use guidance.

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