Skip to main content
Glama
Sign In
Telegram MCP

Telegram MCP

by Anonymouse8882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_sticker_set

Get all stickers in a Telegram sticker set by providing the short name. Lists every sticker from the specified sticker pack.

Instructions

看一个贴纸包里都有哪些贴纸（贴纸包链接 t.me/addstickers/xxx 里的 xxx 就是 short_name）。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "short_name": "<short_name>"
    },
    "name": "get_sticker_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
short_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'see what stickers are in a sticker pack', implying a read-only operation, but does not disclose any behavioral aspects like permissions, rate limits, or error scenarios. Minimal disclosure.

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 sentence that efficiently conveys the purpose and a practical tip. It is concise and front-loaded, with no wasted words.

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?

Given the tool's simplicity (one required parameter, read-only, with an output schema), the description is adequate. It covers the core functionality and parameter derivation. Could mention potential errors but not essential for basic use.

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

Parameters4/5

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

Schema description coverage is 0%, but the description adds significant meaning by explaining that short_name is the xxx in t.me/addstickers/xxx. This helps the agent understand how to obtain the parameter value, going beyond the bare schema.

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 shows stickers in a pack and explains how to obtain the short_name from a link. It implies retrieving the contents of a specific sticker set, distinguishing from siblings like list_sticker_sets which list available sets.

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 provides a hint about when to use (when you have a sticker pack link) and how to derive the short_name, but does not explicitly mention when not to use or alternatives. Usage is implied rather than explicit.

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