Skip to main content
Glama
ATOM00blue

Drin MCP Server

by ATOM00blue

resume_campaign

Resume a paused campaign and continue dispatch from where it left off, returning to the previous lane (sending or scheduled).

Instructions

Resume a paused campaign — it returns to the lane it was paused from (sending if it had started, scheduled otherwise) and dispatch picks up where the cursor left off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCampaign id.
senderNoProduct/sender externalId sent as X-Drin-Sender. Required only for account-wide API keys; overrides the server's default sender.
Behavior4/5

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

With no annotations, description provides good detail on state transition: returns to lane it was paused from and continues dispatch. However, lacks information on permissions, error conditions, and idempotency.

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?

Single sentence, front-loaded with key information. No redundancy; every word adds value.

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

Completeness3/5

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

No output schema, so return value is not described. For a mutation tool, mentioning what is returned would be helpful. Missing prerequisites and error cases. Partially complete but leaves gaps.

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 100%—both parameters are described. The description adds no new meaning beyond the schema, so baseline 3 is 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?

Clear verb and resource: 'Resume a paused campaign'. Distinguishes from siblings like pause_campaign, and explains the lane behavior (sending or scheduled) which adds specificity.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., send_campaign, approve_campaign). Does not mention prerequisites (campaign must be paused) or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ATOM00blue/drin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server