Skip to main content
Glama
Sign In
codex-telegram

codex-telegram

by briejhxh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

telegram_search_media

Read-only

Searches a specified chat for recent media messages including photos, videos, documents, audio, voice notes, animations, and URLs, returning only message metadata without downloading files.

Instructions

Find recent photos, videos, documents, audio, voice notes, animations, or URL messages inside one known chat. Returns message metadata only; no media is downloaded automatically.

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": {
      "chat_id": "<chat_id>",
      "kind": "<kind>"
    },
    "name": "telegram_search_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
limitNo
queryNo
chat_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description clearly discloses that no media is downloaded automatically and only message metadata is returned, fully revealing side effects.

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 concise, information-dense sentences with no filler or redundancy; the essential purpose and side-effect constraint are front-loaded.

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?

The description is adequate for basic intent but lacks guidance on how 'query' filters results and what 'limit' controls. No output schema exists, so return metadata is only briefly described.

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?

With 0% schema coverage, the description must explain parameters. It partially covers 'kind' by enumerating media types and implies 'chat_id' via 'known chat', but fails to explain 'query' and 'limit' entirely.

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?

Description clearly states the tool finds recent media messages of specific types within a single known chat, and explicitly distinguishes itself from file download by noting it returns metadata only.

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 when to use it (targets media in a known chat) but does not explicitly contrast with sibling tools like telegram_search_messages or telegram_download_file, leaving some selection ambiguity.

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