Skip to main content
Glama
Sign In

SelieeAI

by io.github.neebloltd
OverviewDiscussionsAdmin

Create WP Campaign

create_wp_campaign
Destructive

[write] Creates a DRAFT WhatsApp campaign (the result has its id and uuid); nothing is sent until it is started in the panel, which needs the merchant's confirmation that the recipients opted in. wp_account_id / wp_account_uuid is the sending account and the template (wp_template_id / wp_template_uuid) must be APPROVED and belong to it (see list_wp_templates); a campaign sends that one template to everyone. wp_campaign_params are the recipient variable names that fill the template body parameters {{1}}, {{2}}, ... in order (as many as the body has), e.g. ["name", "code"]. Templates with a media header are not supported. wp_campaign_schedule_datetime (ISO 8601) is when it goes out once started. A saved list (wp_list_id or wp_list_uuid; see list_wp_lists) adds all its numbers as recipients; numbers on the opt-out list are kept as skipped.

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": {
      "wp_campaign_title": "<wp_campaign_title>"
    },
    "name": "create_wp_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
wp_list_idNo
wp_list_uuidNo
wp_account_idNo
wp_template_idNo
wp_account_uuidNo
wp_template_uuidNo
wp_campaign_titleYes
wp_campaign_paramsNo
wp_campaign_schedule_datetimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the created entity is a draft, nothing is sent until started in the panel with merchant opt-in confirmation, opt-out numbers are kept as skipped recipients, and media-header templates are unsupported. These are real operational constraints that the destructiveHint/openWorldHint flags alone could not convey.

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?

Front-loaded with the [write] tag and the draft-creating outcome, then parameter guidance in rough priority order. It is dense and long-ish for a description, with some run-on clauses, but every sentence carries substantive constraint information rather than filler.

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

Completeness5/5

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

For a 9-parameter mutation tool with no output schema and no schema descriptions, the description covers the lifecycle (draft, not sent), prerequisites, parameter meanings, and an unsupported-case exclusion. An agent has enough to call it correctly without further exploration.

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?

With 0% schema description coverage, the description carries the load and does so well: it defines the account id/uuid pair as the sending account, requires the template id/uuid to be APPROVED and owned by that account, explains that wp_campaign_params are ordered variable names filling {{1}}, {{2}}..., gives ISO 8601 for the schedule datetime, and explains list id/uuid behavior. Only wp_campaign_title is left unremarked, which is the one minor gap.

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?

Opens with a specific verb and resource plus the key qualifier: it creates a DRAFT WhatsApp campaign and returns its id and uuid. The WhatsApp qualifier distinguishes it cleanly from the many sibling campaign creators (create_sms_campaign, create_tg_campaign, create_email_campaign, create_voip_campaign).

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 use: the template must be APPROVED and belong to the sending account, and it points to list_wp_templates and list_wp_lists for prerequisites. It also rules out media-header templates. It does not, however, explicitly contrast with send_wp_template for one-off sends, so the alternative routing is only implied.

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

All SelieeAI 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