VibeAdmin

Create an email draft

create_email_draft

Create a broadcast DRAFT for a human to review and send from the dashboard. Nothing is emailed. Merge tags: {{first_name|there}}, {{name}}, {{plan}}. Marketing/product_updates get an unsubscribe footer automatically.

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": {
      "subject": "<subject>",
      "html": "<html>"
    },
    "name": "create_email_draft"
  }
}

Input Schema

Name	Required	Description	Default
`html`	Yes	Email body as HTML with inline styles.
`plan`	No	Only users on this plan (optional).
`subject`	Yes
`category`	No		marketing
`segment_id`	No	Send to a saved segment (see list_segments). Overrides plan.
`preview_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare non-read-only, non-destructive, closed-world, so the safety profile is partly covered. The description adds real value by clarifying nothing is sent, the draft is reviewed manually, merge tags are available, and an unsubscribe footer is auto-added for marketing/product_updates. It does not describe what is returned (e.g., draft ID) or how the draft can be subsequently fetched/edited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences with no waste; the most important constraint ('Nothing is emailed') comes immediately after the purpose. The merge-tag list is compact and useful rather than filler.

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?

Given no output schema and modest complexity, the description covers purpose, safety, and key formatting behavior. It would be complete if it described the returned draft identifier and the segment_id-overrides-plan behavior already hinted in the schema.

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 50%, so half the parameters lack descriptions. The description adds meaning for html (merge tag syntax) and category (auto unsubscribe footer), but says nothing about preview_text or the plan/segment_id interaction, which the schema only partially explains.

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+resource ('Create a broadcast DRAFT') plus the key scope qualifier 'for a human to review and send from the dashboard'. This cleanly separates it from the sibling send_email tool without needing to name it.

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?

'Nothing is emailed' and 'for a human to review and send from the dashboard' communicate the review-then-send workflow, implicitly routing actual sending to send_email. It stops short of explicitly naming the alternative or stating when-not to use it.

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

All VibeAdmin tools Inspect

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.