Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_telegram_channel_direct_send

Sends one approved plain-text message to a Telegram channel's Direct Messages after a preflight check confirms DMs are enabled. Requires confirm=true and never posts to the channel feed.

Instructions

Send one explicitly approved plain-text message to a Telegram channel's Direct Messages monoforum, only when a read-only preflight confirms that Direct Messages are enabled. Requires Telegram Premium and confirm=true; never publishes to the channel feed.

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": {
      "channel": "<channel>",
      "text": "<text>",
      "confirm": "<confirm>"
    },
    "name": "ads_telegram_channel_direct_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
channelYes@username or t.me public channel
confirmYesExplicitly confirm sending this one channel Direct Message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden well: it discloses the Premium requirement, confirmation requirement, preflight dependency, single-message scope, plain-text restriction, and that it does not post to the channel feed. It does not cover response shape, failure modes, or rate limits, so it is strong but not exhaustive.

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 dense sentences with the core action and constraints front-loaded. Every clause contributes either scope, prerequisites, or behavioral constraints.

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?

For a three-parameter mutation tool with no annotations and no output schema, the description covers the essential call conditions and side-effect scope. It leaves return behavior and error handling unspecified, but an agent has enough information to invoke it correctly.

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 coverage is 67%; channel and confirm are already described in the schema, and text has only type and length constraints. The description adds that the message is plain-text and limited to one message, plus that confirm=true is required, but it does not add much parameter-specific meaning beyond the schema.

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 states a specific verb and resource: sending one plain-text message to a Telegram channel's Direct Messages monoforum. It also distinguishes this action from publishing to the channel feed, so an agent can tell it apart from broader Telegram send tools.

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 gives explicit conditions: use only when a read-only preflight confirms Direct Messages are enabled, requires Telegram Premium, and confirm=true. It also states a clear exclusion, never publishing to the channel feed, though it does not name the specific preflight sibling 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