Skip to main content
Glama
Sign In
telegram-api-mcp

telegram-api-mcp

by EngDawood
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_trail

Read-onlyIdempotent

Query the TRAIL content log to check which content was posted, failed, or skipped across pipelines.

Instructions

Query the TRAIL content log. Check what content was posted, failed, or skipped across pipelines.

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries, newest first (default: 50, 0 = all)
sinceNoISO 8601 timestamp — only entries after this time
actionNoFilter by action (posted, failed, skipped, etc.)
offsetNoEntries to skip for pagination (default: 0)
trace_idNoFilter by pipeline trace ID
requesterNoFilter by workflow/task ID
content_idNoFilter by content ID (exact or prefix like 'civitai:image:')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the log tracks posted/failed/skipped statuses across pipelines, but does not disclose additional behavioral traits like pagination limits or response format. No contradiction with annotations.

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 sentences, front-loaded with the main verb and resource, and no wasted words. Every sentence contributes to understanding.

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 well-documented schema and strong annotations, the description covers the essential purpose. It lacks explicit mention of the return format, but for a read-only query tool with no output schema, the description is sufficient for agent invocation.

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%, so all 7 parameters are already fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

The description clearly states the tool queries the TRAIL content log and specifies what it checks (posted, failed, or skipped content across pipelines). This distinguishes it from siblings like get_trail_stats (statistics) and mark_trail (marking entries).

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?

The description gives clear context for use: inspecting content log entries by status. It does not explicitly mention exclusions or alternatives, but the purpose is unambiguous enough for an agent to decide when to invoke this tool.

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