Skip to main content
Glama
Sign In
viber-mcp

viber-mcp

by serhiizghama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

broadcast_message

Send the same text message to up to 300 Viber recipients simultaneously.

Instructions

Send the same text message to up to 300 Viber users at once

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": {
      "receivers": "<receivers>",
      "text": "<text>"
    },
    "name": "broadcast_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiversYesUp to 300 receiver IDs
textYesMessage text, up to 7000 characters
sender_nameNoDisplay name override (≤28 chars)
sender_avatarNoAvatar URL override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behaviors. It only states the basic action and limit, but omits important details like whether delivery status is returned, error handling, rate limits, or idempotency.

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 a single, clear sentence of 12 words with no unnecessary information, making it highly concise and well-structured.

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?

The tool sends messages and has no output schema. The description fails to explain what the function returns (e.g., success status, failed receivers), leaving a significant gap for an agent to understand the result.

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 100% with adequate descriptions for each parameter. The tool description adds no additional meaning beyond 'send the same text message,' so it does not improve upon 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 'Send the same text message to up to 300 Viber users at once' clearly states the action and resource, and distinguishes from siblings like send_message (single user) by specifying the broadcast nature and user limit.

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 description implies use for broadcasting to multiple users but does not explicitly mention when to use or avoid this tool, nor does it reference alternatives like send_message for individual messages.

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