Skip to main content
Glama

resume_agent

Resume a paused agent to restart scheduled outreach actions in the Swarmix-MCP server for LinkedIn, Email, X, Instagram, and Blog campaigns.

Instructions

Resume a paused agent. It will start running scheduled actions again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesThe agent ID to resume

Implementation Reference

  • The handler function for the resume_agent tool, which calls the client's resumeAgent method.
    handler: async (args: Record<string, unknown>) => {
      const result = await client.resumeAgent(args.agentId as string);
      return JSON.stringify(result, null, 2);
    },
  • The tool registration definition for resume_agent in src/tools/agents.ts.
    {
      name: 'resume_agent',
      description: 'Resume a paused agent. It will start running scheduled actions again.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          agentId: { type: 'string', description: 'The agent ID to resume' },
        },
        required: ['agentId'],
      },
      handler: async (args: Record<string, unknown>) => {
        const result = await client.resumeAgent(args.agentId as string);
        return JSON.stringify(result, null, 2);
      },
    },
  • The underlying API client method that performs the actual network request to resume an agent.
    async resumeAgent(id: string) {
      return this.request('PUT', `/api/agents/${id}`, { status: 'active' });
    }
Behavior3/5

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

Annotations are absent, so description carries full burden. It adds valuable behavioral context that 'scheduled actions' will resume, but omits idempotency, error states (what happens if agent isn't paused), and side effects.

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?

Two efficient sentences with zero waste. Front-loaded with the action (resume), followed by behavioral consequence. Appropriate length for single-parameter tool.

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?

Adequate for low-complexity tool (1 param, no output schema, flat structure) with 100% schema coverage. However, given zero annotations and state-changing nature, gaps exist regarding error handling and state validation.

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?

Schema coverage is 100%, establishing baseline 3. Description adds semantic value by implying the agentId must refer to a 'paused' agent, providing necessary context beyond the schema's plain ID description.

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?

Specific verb 'Resume' + resource 'agent' clearly stated. The phrase 'scheduled actions again' effectively distinguishes this from sibling 'run_agent' (immediate execution) and implies the inverse relationship to 'pause_agent'.

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

Usage Guidelines3/5

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

Implies prerequisite state ('paused agent') but lacks explicit when-to-use guidance or warnings against using on already-active agents. No explicit alternatives mentioned despite relevant siblings existing.

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/diegotorreslopez81/swarmix-mcp'

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