Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by dikaglorya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List blocked users

telegram_list_blocked
Read-only

Retrieve the users your Telegram account has blocked, including IDs, names, usernames, and block timestamps, with pagination via limit and offset.

Instructions

List the users this account has blocked (id, name, username, blocked-at).

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_list_blocked"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by enumerating the returned fields (id, name, username, blocked-at) in the absence of an output schema, but says nothing about pagination behavior, ordering, or the limit cap of 100.

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?

A single front-loaded sentence with no filler; the parenthetical return-field list earns its place because no output schema exists. Nothing could be removed without losing information.

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 read-only list tool with annotations covering safety, the description tells the agent what it does and what it returns. The only real gap is pagination/ordering semantics for limit and offset, which is minor but would matter for large block lists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters (limit, offset), so the description is expected to compensate and does not mention either. The schema's own defaults and bounds (max 100, min 1) provide structural hints, but paging semantics are undocumented anywhere.

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?

States a specific verb ('List') and a precisely scoped resource ('the users this account has blocked'), which is clearly distinct from siblings like telegram_block_user, telegram_get_contacts, and telegram_search_users. An agent can identify the tool's role without opening the schema.

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 when-to-use guidance, no mention of the counterpart telegram_block_user for unblocking, and no statement of when this is preferable to telegram_get_contacts or telegram_search_users. The description offers no routing context at all.

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