Sparetext

Start a campaign

create_campaign

Start a campaign draft: one message to a big list (up to 100,000 people) sent slowly from the user's Android phones so carriers don't filter their SIMs. Nothing is sent. Add people with update_campaign, send a test with send_campaign_test, then ask the owner to launch it with request_campaign_launch. Only for people who know the sender: past customers, attendees, members.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_campaign"
  }
}

Input Schema

Name	Required	Description
`ask`	No	The question people last seen over 5 years ago get first; only a YES gets them the text. On by default.
`from`	No	Who the texts are from, said first, e.g. XYZ Events
`lang`	No	The text's language code (en, es, fr…): replies are read in it
`name`	No	Its name, for the user only
`sims`	No	The SIMs it sends from, as get_campaign lists them
`text`	No	The text. Blanks: {{first_name}}, {{name}}, {{event}}, {{year}}, with a fallback like {{first_name\|there}}. How to stop is added to each person's first text.
`hours`	No	Sending hours in the recipients' own time; 09:00 to 20:00 every day unless changed, and always kept inside a texted country's own rule
`limits`	No	Optional: a slower pace per SIM, in SMS parts. It can't go faster.
`mid_line`	No	Optional line for people last seen 2 to 5 years ago, e.g. You came to {{event}} in {{year}}.
`start_at`	No	Optional: not before this (within 60 days)
`finish_by`	No	Optional: when it should be done; the plan says if it fits
`other_countries`	No	Also text the list's numbers from other countries (left out by default)

Output Schema

Name	Required	Description	Default
`url`	Yes
`campaign`	Yes
`simChoices`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / hours / description

Previous value: -"Sending hours in the recipients' own time; 09:00 to 20:00 every day unless changed"New value: +"Sending hours in the recipients' own time; 09:00 to 20:00 every day unless changed, and always kept inside a texted country's own rule"

AddedOct 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark this as non-read-only, non-destructive and non-idempotent. The description adds critical context beyond the annotations: nothing is sent at this stage, sending is intentionally slow to avoid carrier filtering, the list can be up to 100,000 people, and an owner must separately launch the campaign.

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?

The description is front-loaded with the essential action and draft status, then moves to workflow and eligibility. Every sentence is useful, though it is slightly dense and could be split for easier scanning.

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?

Given the output schema exists and the input schema has 100% description coverage, the description fills the remaining gaps an agent needs: draft semantics, follow-up steps, scale, pacing rationale, and audience eligibility. Nothing essential for correct invocation appears to be missing.

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 every parameter is already documented in the input schema. The description reinforces scale ('up to 100,000 people') and the draft nature but does not add parameter-level syntax or meaning beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 names a specific verb and resource ('Start a campaign draft') and immediately scopes it to 'one message to a big list' sent from Android phones. It clearly distinguishes this tool from related siblings by describing the draft-only nature and the follow-up workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool and names alternatives at each workflow step: 'Add people with update_campaign, send a test with send_campaign_test, then ask the owner to launch it with request_campaign_launch.' It also provides an eligibility rule: 'Only for people who know the sender'.

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

All Sparetext 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.

Resources

Need Help?