Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_telegram_ads_api_increase_ad_budget

Increase a Telegram Ads ad budget through the official API; requires confirm=true for this provider write.

Instructions

Increase one Telegram Ads ad budget through the official API. This is a provider write; confirm=true is required.

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": {
      "ad_id": "<ad_id>",
      "amount": "<amount>",
      "confirm": "<confirm>"
    },
    "name": "ads_telegram_ads_api_increase_ad_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYes
amountYes
confirmYes
account_idNo
timeout_msNo
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 usefully discloses that this is a provider write and that confirm=true is required, but it omits permissions, reversibility, side effects, rate limits, and return behavior.

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 short sentences are front-loaded with the action and the key confirmation requirement. There is no filler.

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?

This is a mutation tool with no annotations, no output schema, and six undocumented parameters. The description covers the write nature and confirmation flag but leaves too much unspecified for an agent to call it confidently.

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?

Schema description coverage is 0% across six parameters. The description explains only the confirm requirement and says nothing about ad_id format, amount semantics, account_id, timeout_ms, or idempotency_key.

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 states a specific verb and resource: increase one Telegram Ads ad budget through the official API. This clearly distinguishes it from create-ad or set-paused siblings, though it does not explicitly name alternatives.

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 verb 'increase' implies the intended use, and confirm=true is stated as a prerequisite. However, there is no explicit guidance on when to use this versus other Telegram Ads API tools, nor any exclusions or amount constraints.

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