Skip to main content
Glama
Sign In

HelpWell

by ai.helpwell.app
OverviewDiscussionsAdmin

Schedule a newsletter

schedule_newsletter
Destructive

Sends a newsletter to its audience: now, at a time, at a local time in each contact’s time zone, or at each contact’s best time on a day. A draft is marked ready first. Once scheduled it can only be cancelled with cancel_newsletter.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "schedule_newsletter"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave out first: the tool then says exactly what will happen and changes nothing. Pass true only after the person has seen that and said yes.
sendModeNofixed: at scheduledAt (now when left out). local: localTime in each contact’s zone. best: the localTime date at each contact’s usual opening hour.
localTimeNoYYYY-MM-DDTHH:mm, for local and best.
campaignIdYesNewsletter id from list_newsletters.
scheduledAtNoISO date and time, for fixed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false, openWorldHint=true), the description adds real behavioral context: the draft is marked ready as a side effect, and the action is effectively irreversible except through cancel_newsletter. The confirm-parameter preview flow in the schema further discloses that no change occurs until confirmed. It stops short of describing permissions or audience-side effects.

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 tightly written sentences with the core action and timing options front-loaded, followed by the readiness and irreversibility constraints. No redundant or filler text.

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 scheduling/mutation tool with a fully documented schema and annotations covering the safety profile, the description supplies the missing behavioral pieces (ready-marking, irreversibility, cancel-only escape). It is not fully exhaustive on audience permissions or scheduling limits, but no critical calling information is absent.

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 description coverage is 100%, so the schema already documents all five parameters including the sendMode enum mapping and the confirm two-step flow. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (sends/schedules) and resource (a newsletter), and enumerates the four distinct send timings so an agent knows exactly what the tool offers. It also names the sibling relationship with cancel_newsletter, distinguishing it from other newsletter 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?

Gives clear context for each mode (now/at a time/local time/best time) and states the key precondition that a draft is marked ready first and the only post-scheduling escape is cancel_newsletter. It does not, however, explicitly contrast this with nearby siblings like send_test_newsletter or preview_newsletter.

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

All HelpWell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources