Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_telegram_ads_sync

Read Telegram Ads metrics and save campaigns, daily spend, and optional time-bucketed stats to local SQLite without modifying Telegram Ads.

Instructions

Read Telegram Ads metrics and persist campaigns, daily spend and optional time-bucketed metrics into local SQLite. This never writes to Telegram Ads.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_telegram_ads_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_adsNo
list_toolNo
module_idNo
project_idNo
stats_toolNo
stats_periodNo
include_statsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden. It discloses that the tool reads from Telegram Ads and writes to local SQLite, and importantly states it never writes to Telegram Ads. However, it lacks details on sync behavior (full vs incremental), error handling, permissions, or rate limits.

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 two sentences, front-loaded with the core action and followed by a key constraint. It is appropriately sized, though it could be slightly more detailed without becoming verbose.

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

Completeness2/5

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

Given 7 parameters, no annotations, and no output schema, the description is incomplete. It omits parameter explanations, usage guidance, and many behavioral details necessary for an agent to call the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the 7 parameters (max_ads, list_tool, module_id, project_id, stats_tool, stats_period, include_stats). It only generically mentions 'optional time-bucketed metrics', leaving all parameter meanings undocumented.

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 a specific verb (read) and resources (Telegram Ads metrics, campaigns, daily spend, time-bucketed metrics) and includes a key constraint (never writes to Telegram Ads). However, it does not differentiate from sibling sync/report tools like ads_telegram_ads_api_sync or ads_telegram_ads_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. It implies usage for syncing Telegram Ads data to local SQLite, but does not mention any conditions, prerequisites, or alternative tools.

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