rapid-indexer-mcp

Create AI traffic campaign

create_traffic_campaign

Send configurable AI-driven human-like visitors to any URL with geo, device, and behavior settings. Create a campaign to increase page visits and engagement.

Instructions

Send AI-driven, human-like visitors to a URL (geo, device, referrer and on-page behaviour are configurable). SPENDS CREDITS immediately: see get_pricing (credits per 1,000 visitors). visitors/days must not exceed 1,000 per day. Confirm with the user before creating. Returns the task id; poll get_task for status.

Input Schema

Name	Required	Description	Default
`days`	No	Spread the visitors over this many days.
`link`	Yes	Target page the visitors should land on.
`title`	No	Campaign name shown in the dashboard.
`device`	No		mixed
`country`	No	Visitor geo. WW = worldwide mix.	WW
`referrer`	No	Apparent traffic source, e.g. "facebook.com" or a full URL. Empty = direct.
`visitors`	Yes	Total visitors to send (min 30, max 1,000 per scheduled day).
`delay_max`	No	Max seconds on page.
`delay_min`	No	Min seconds on page.
`pages_max`	No	Max internal pages per visit.
`pages_min`	No	Min internal pages per visit.
`ai_enabled`	No	Human-like AI browsing (scrolling, reading, internal clicks).
`bounce_rate`	No	Percent of single-page visits.
`click_links`	No	Paths or CSS selectors the visitor may click, e.g. ["/pricing", "button.cta"].
`click_chance`	No	Percent of visitors who click one of click_links.
`video_chance`	No

Output Schema

Name	Required	Description	Default
`days`	Yes
`status`	Yes
`message`	Yes
`task_id`	Yes
`ctr_mode`	No
`visitors`	Yes
`campaign_id`	Yes
`dashboard_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Discloses non-obvious side effects not present in annotations: immediate credit consumption, a 1,000/day pacing cap, and the async return of a task id requiring polling. This goes well beyond the structured hints (readOnly=false, idempotent=false) and gives the agent the cost and confirmation guardrails it needs.

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?

Five short sentences, each adding distinct value: main action, cost warning, pacing limit, user confirmation, and follow-up polling. The most important information is front-loaded and there is no 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 16 parameters, the description plus a rich schema covers the full create-and-monitor workflow, including cost, limit, confirmation, and status retrieval. It is complete enough for an agent to call the tool safely and know what to do next; the only minor gap is not mentioning the CTR-campaign alternative.

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 88%, so the schema carries most parameter meaning; the description adds little beyond naming configurable dimensions and restating the daily cap already encoded in visitors' description. It does not clarify the one undocumented parameter (video_chance), so a baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description opens with a concrete action ('Send AI-driven, human-like visitors to a URL') and names configurable dimensions (geo, device, referrer, on-page behavior). It clearly identifies the resource and outcome, though it does not explicitly contrast with sibling create_ctr_campaign, so it stops short of full sibling differentiation.

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?

Provides strong operational context: credits are spent immediately, check get_pricing, confirm with the user before creating, and poll get_task for status. It does not explicitly state when to choose this over create_ctr_campaign, but the workflow guidance is clear enough for an agent to act.

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

Deploy Server