telegram-ads-mcp

Overview Schema Source Related Servers Discussions Admin

check_session

Read-onlyIdempotent

Verify whether your ads.telegram.org session is still valid and retrieve owner, cabinet, currency, and balance details. If authentication fails, obtain step-by-step DevTools instructions to reauthenticate securely.

Instructions

Ping the current ads.telegram.org session.

Returns owner_id, cabinet (ton/eur/stars), currency, balance.
Does not return api_hash or cookies. Stars cabinets are reported but not used.
If ok=false with code=auth, offer INSTALL.md DevTools steps; they write .env (never paste into chat); then reload_session.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses exact returned fields (owner_id, cabinet, currency, balance), intentional omissions (api_hash, cookies), the caveat about Stars cabinets, and the secure auth-failure workflow. This is high-value behavioral context, especially around secret handling.

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?

The description is four tight sentences with no filler. The core action is front-loaded, followed by essential output details, exclusions, and failure handling. Every sentence contributes meaningful information.

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

Completeness5/5

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

With no parameters, a provided output schema, and clear annotations, the description covers everything needed to invoke and react to the tool: what it checks, what it returns, what it avoids returning, and how to recover from auth failure.

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?

The tool has zero parameters and schema coverage is 100%, so the empty input schema fully documents the interface. The description reinforces the session-scoped nature by saying 'current session,' which is sufficient at the baseline for no-parameter tools.

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 opens with a specific verb and resource: 'Ping the current ads.telegram.org session.' It then clarifies what the tool returns and explicitly states what it does not return, making it easy to distinguish from siblings like reload_session or get_account.

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?

It clearly indicates this is a session health-check tool and provides a concrete next step on auth failure: offer INSTALL.md DevTools steps, write .env, then reload_session. It does not explicitly contrast with alternatives like get_account, but the intended usage context is clear.

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