Skip to main content
Glama

batch_send

Send content to multiple users, groups, or chats in a single call. Each target is dispatched sequentially with a configurable delay, and per-target success or error is reported. Ideal for broadcasting messages across Feishu.

Instructions

[User Identity / Official API] Send the same or different content to multiple targets in one call. Each target dispatches sequentially with a small delay (anti-rate-limit) and reports per-target success/error. Identity is the cookie user (user-identity sends) unless target.via=bot. Use for broadcast / fan-out scenarios.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYesArray of targets. Each entry: { type: "user"|"group"|"chat", id: <user_name | group_name | chat_id>, content: { kind: "text"|"image"|"file"|"post", ... } }. For kind="text": { text }. For "image": { image_key }. For "file": { file_key, file_name }. For "post": { title, paragraphs }. Optional per-target: via="bot" routes through send_message_as_bot (chat_id required).
delay_msNoDelay between sends in milliseconds (default 200, increase for risky volumes).
Behavior4/5

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

With no annotations, the description carries full burden. It states sequential dispatch with delay, per-target success/error reporting, and identity rules. It does not detail rate limits or error handling for the entire call, but it is fairly transparent for a send action.

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?

Four sentences, each serving a clear purpose: purpose, behavior, identity, and usage. No wasted words, front-loaded with main action. Highly concise and structured.

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

Completeness3/5

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

The description lacks return value format or error structure. Per-target success/error is mentioned but not described. For a batch tool, the response format is important for handling results. Also no mention of empty targets or other edge cases.

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?

Schema coverage is 100%, providing parameter descriptions. The description adds value by explaining the array structure, via=bot routing, and default delay. This goes beyond the schema, which only describes fields. So a 4 is warranted.

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 clearly states it sends content to multiple targets in one call, using the verb 'send' and resource 'multiple targets'. It differentiates from sibling tools by noting sequential dispatch with delay and per-target success/error. Also specifies identity context and via=bot routing.

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?

The description explicitly says 'Use for broadcast / fan-out scenarios.' It also implies context (identity rules, via=bot). While it does not explicitly state when not to use or name alternatives, it provides enough context for an agent to decide.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EthanQC/feishu-user-plugin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server