Skip to main content
Glama

Post to Newsletter

neuron_post_to_newsletter

Post text, image, video, or document to a WhatsApp Channel newsletter. All subscribers receive the message.

Instructions

Post a message (text, image, video, or document) to a WhatsApp Channel newsletter. All subscribers will receive the message. Provide at least one of text or mediaUrl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the newsletter
textNoThe message text or caption to post
mediaUrlNoURL of the media file to attach (image, video, or document)
messageTypeNoThe type of message to sendtext
Behavior3/5

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

No annotations provided, so description carries full burden. States 'all subscribers will receive the message' but lacks disclosure of permissions, irreversibility, or side effects. Adequate for a posting action but not thorough.

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 concise sentences. First sentence delivers core purpose; second adds key constraint. No redundant or extraneous information.

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?

Description is adequate for a low-complexity posting tool. Covers purpose, supported content, audience, and a constraint. Lacks return value description but that is often self-evident. Missing details on error handling or validation.

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 covers 100% of parameters with descriptions. Description adds valuable constraint ('at least one of text or mediaUrl') not present in schema's required field. Also clarifies that text can be used as a caption alongside media.

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?

Description clearly states the action (post), resource (WhatsApp Channel newsletter), content types (text, image, video, document), and scope (all subscribers). Distinct from sibling tools like neuron_create_newsletter or neuron_send_message.

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?

Description provides a precondition ('Provide at least one of text or mediaUrl') but does not explicitly specify when to use this tool versus alternatives like neuron_send_broadcast or neuron_send_message. Usage context is implied but lacks exclusion criteria.

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/conquext/neuron-mcp-server'

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