Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by dikaglorya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List a user's profile photos

telegram_user_photos
Read-only

Retrieve a user's profile photos, including photo IDs, sizes, and downloadable file references for review or download.

Instructions

List the profile photos of a user (or of 'me'). Returns photo ids with their sizes and a downloadable file reference; use telegram_download_media only for chat messages, not for these.

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

Input Schema

NameRequiredDescriptionDefault
userNome
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so the bar is lower, and the description adds real value by describing the return payload (photo ids, sizes, a downloadable file reference). It doesn't cover ordering, freshness, or privacy/visibility restrictions, so not a 5.

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 tight sentences: the purpose first, then the return shape and the sibling-routing caveat. No redundancy.

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

Completeness3/5

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

No output schema exists, and the description does cover the returned fields, which is good. However, with three undescribed parameters including pagination controls, an agent still lacks enough information to page through results correctly.

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% across three parameters, and the description only hints that 'user' accepts 'me'. The meaning of 'limit' and 'offset' and their pagination behavior are left entirely undocumented in both schema and description.

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 and resource ('List the profile photos of a user') and clarifies the 'me' self-target case. It is clearly distinct from siblings like telegram_set_my_photo or telegram_set_chat_photo, which write rather than read.

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

Usage Guidelines4/5

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

Explicitly routes the agent away from telegram_download_media for these items ('use telegram_download_media only for chat messages, not for these'). It doesn't spell out when to prefer telegram_full_user over this, but the boundary with the download sibling is stated.

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