Skip to main content
Glama
TONresistor

Telegram MCP Server

by TONresistor

getChatGifts

Retrieve gifts owned by a chat with filters for saved, unique, unlimited, and blockchain-transferred items, plus sorting by price and pagination.

Instructions

Returns the gifts received and owned by a chat. Returns an OwnedGifts object on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of gifts to be returned; 1-100. Defaults to 100.
offsetNoOffset of the first entry to return as received from the previous request.
chat_idYesUnique identifier for the target chat or username of the target channel (format: @channelusername).
exclude_savedNoPass True to exclude gifts that are saved to the chat's profile page.
sort_by_priceNoPass True to sort results by gift price instead of send date. Sorting is applied before pagination.
exclude_uniqueNoPass True to exclude unique gifts.
exclude_unsavedNoPass True to exclude gifts that are not saved to the chat's profile page.
exclude_unlimitedNoPass True to exclude gifts that can be purchased unlimited number of times.
exclude_from_blockchainNoPass True to exclude gifts transferred from the TON blockchain.
exclude_limited_upgradableNoPass True to exclude limited gifts that can be upgraded.
exclude_limited_non_upgradableNoPass True to exclude limited gifts that cannot be upgraded.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add the return type OwnedGifts and success behavior, but it provides no detail on error cases, pagination semantics, or side effects. The verb 'Returns' implies a read operation, yet this is not made explicit.

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 short and front-loaded, stating the primary purpose first and then the return type. There is mild redundancy with 'Returns' used twice, but the overall structure is efficient and easy to scan.

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?

This is minimally viable: the description names the resource and output type, and the schema covers all parameters. However, it lacks sibling differentiation, deeper behavioral context, and explanation of the OwnedGifts shape, which matters because no output schema is provided.

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%, and the input schema already documents all parameters with individual descriptions and constraints. The tool description adds no parameter-level meaning, so the coverage baseline of 3 applies.

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 identifies a specific verb and resource: it returns gifts received and owned by a chat. It is clear and unambiguous, but it does not explicitly distinguish this tool from closely related siblings like getUserGifts or getAvailableGifts.

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?

The description implies this should be used to retrieve gifts belonging to a chat, but it never explicitly states when to choose it over alternatives such as getUserGifts or getBusinessAccountGifts. No when-not-to-use guidance or exclusion criteria are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TONresistor/telegram-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server