redreplier

Activate Pending Keywords

activate_pending_keywords

Activate every pending keyword in one pass: free plan-covered slots are promoted immediately, and a prorated upgrade charge covers the rest. Keywords stay pending until payment settles, then become active; recheck websites.

Instructions

Activate every PENDING keyword across the account in two steps: promote as many as the current plan covers for free, then charge an immediate prorated upgrade to cover the remainder (keywords disabled this cycle still hold slots and count). Keywords covered by the upgrade stay PENDING in the response and flip ACTIVE once the payment settles; re-check with list_websites. Always call preview_activate_pending first, show the user immediateCharge and targetPlanName, and get explicit consent; never call this in a loop. Use enable_keyword for a single DISABLED keyword. Fails with 400 when there is no active subscription or the charge fails, leaving keywords PENDING. Returns the updated websites.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	All websites with their keyword statuses; keywords waiting on an upgrade payment still show PENDING.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Sep 7, 2026

changedOutput schema / properties / result / description

Previous value: -"The updated websites reflecting the newly activated keyword statuses."New value: +"All websites with their keyword statuses; keywords waiting on an upgrade payment still show PENDING."

First observedv0.1.0Sep 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false), so the description carries the full burden. It discloses the two-step billing process, that keywords stay PENDING until payment settles, the immediate prorated charge, and the failure behavior. It also warns against looping, which is critical behavioral context.

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?

The description is long but every sentence earns its place: it front-loads the core action, then covers billing behavior, prerequisites, alternatives, and failure modes. The structure is logical and dense without redundancy.

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 complexity (billing, multi-step process, PENDING state), the description covers all necessary aspects: prerequisite call, user consent, immediateCharge display, targetPlanName, re-check via list_websites, failure modes, and return value (updated websites). Nothing an agent needs is missing.

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?

The tool has zero parameters, so the schema trivially covers 100% of them. The description adds no parameter details because none exist. Baseline for 0 params is 4, and the description does not detract; it's appropriate.

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 states a specific action ('Activate every PENDING keyword across the account') with a clear verb, resource, and scope. It also differentiates itself from siblings by naming enable_keyword for a single DISABLED keyword and preview_activate_pending as a prerequisite, so an agent can distinguish it without inspecting other tools.

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?

Explicitly instructs when to call this tool: after preview_activate_pending, with explicit user consent, and never in a loop. It also specifies the alternative (enable_keyword) for a single DISABLED keyword and notes failure conditions (400 when no active subscription or charge fails). No ambiguity remains.

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