Resume Campaign
neuron_resume_campaignResume a previously paused WhatsApp campaign by providing the campaign ID.
Instructions
Resume a paused campaign
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Campaign ID |
neuron_resume_campaignResume a previously paused WhatsApp campaign by providing the campaign ID.
Resume a paused campaign
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Campaign ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not disclose any behavioral traits such as side effects or permissions required. It only states the action without context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (one sentence), but it lacks structure and does not front-load critical details. It could be slightly expanded without being verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple action, the description is incomplete. It does not mention success/failure outcomes, rate limits, or any preconditions. No output schema exists to compensate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'id', so description adds no additional meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The verb 'resume' and resource 'campaign' are clear. It distinguishes from siblings like pause_campaign and stop_campaign, but does not explicitly contrast with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives (e.g., resume vs start a new campaign). No mention of prerequisites like campaign must be paused.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/conquext/neuron-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server