Skip to main content
Glama

fluentcrm_resume_campaign

Resume a paused FluentCRM email marketing campaign by providing the campaign ID to restart automated workflows and message delivery.

Instructions

Wznawia kampanię

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesID kampanii

Implementation Reference

  • Core implementation of resuming a FluentCRM campaign by making a POST request to the `/campaigns/${campaignId}/resume` API endpoint.
    async resumeCampaign(campaignId: number) {
      const response = await this.apiClient.post(`/campaigns/${campaignId}/resume`);
      return response.data;
    }
  • MCP server CallToolRequestHandler switch case that executes the tool by calling client.resumeCampaign with the input campaignId argument.
    case 'fluentcrm_resume_campaign':
      return { content: [{ type: 'text', text: JSON.stringify(await client.resumeCampaign((args as any)?.campaignId), null, 2) }] };
  • Registration of the 'fluentcrm_resume_campaign' tool in the ListToolsRequestHandler response, defining its name, description, and input schema.
      name: 'fluentcrm_resume_campaign',
      description: 'Wznawia kampanię',
      inputSchema: {
        type: 'object',
        properties: {
          campaignId: { type: 'number', description: 'ID kampanii' },
        },
        required: ['campaignId'],
      },
    },
  • Input schema definition for the tool, specifying that a numeric 'campaignId' is required.
    inputSchema: {
      type: 'object',
      properties: {
        campaignId: { type: 'number', description: 'ID kampanii' },
      },
      required: ['campaignId'],
Behavior1/5

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

No annotations are provided, so the description carries full burden but offers no behavioral details. It doesn't disclose whether this is a read/write operation, what permissions are needed, if it's idempotent, what happens on success/failure, or any side effects (e.g., resuming email sends). This leaves the agent guessing about critical behavioral traits.

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 extremely concise with just two words, front-loading the core action. There is no wasted language, though this brevity contributes to underspecification in other dimensions. For conciseness alone, it earns full marks.

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

Completeness1/5

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

Given the complexity of a campaign management tool with no annotations and no output schema, the description is severely incomplete. It lacks essential context like what 'resuming' means operationally, expected outcomes, error conditions, or dependencies. This leaves the agent ill-equipped to use the tool effectively in a real-world scenario.

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 description coverage is 100%, with the single parameter 'campaignId' documented as 'ID kampanii' (campaign ID). The description adds no additional meaning beyond the schema, such as format examples or constraints. However, with high schema coverage and only one parameter, the baseline of 3 is appropriate as the schema adequately defines the input.

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

Purpose2/5

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

The description 'Wznawia kampanię' (Resumes a campaign) restates the tool name in Polish without adding specificity. It doesn't clarify what 'resuming' entails operationally or distinguish this tool from sibling tools like 'fluentcrm_pause_campaign' or 'fluentcrm_create_campaign'. The purpose is vague beyond the basic verb.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the campaign must be paused), exclusions, or relationships with sibling tools like 'fluentcrm_pause_campaign' or 'fluentcrm_delete_campaign'. The agent receives no contextual cues for appropriate invocation.

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/netflyapp/fluentcrm-mcp-server'

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