Skip to main content
Glama

fluentcrm_pause_campaign

Pause a running FluentCRM email campaign to temporarily stop sending emails to contacts, allowing for campaign adjustments or troubleshooting.

Instructions

Wstrzymuje kampanię

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesID kampanii

Implementation Reference

  • Core handler function that pauses a FluentCRM campaign by sending a POST request to the /campaigns/{campaignId}/pause API endpoint.
    async pauseCampaign(campaignId: number) {
      const response = await this.apiClient.post(`/campaigns/${campaignId}/pause`);
      return response.data;
    }
  • Tool registration entry defining the name, description, and input schema for fluentcrm_pause_campaign.
      name: 'fluentcrm_pause_campaign',
      description: 'Wstrzymuje kampanię',
      inputSchema: {
        type: 'object',
        properties: {
          campaignId: { type: 'number', description: 'ID kampanii' },
        },
        required: ['campaignId'],
      },
    },
  • Input schema defining the required campaignId parameter of type number.
    inputSchema: {
      type: 'object',
      properties: {
        campaignId: { type: 'number', description: 'ID kampanii' },
      },
      required: ['campaignId'],
    },
  • MCP server request handler case that dispatches to the client.pauseCampaign method.
    case 'fluentcrm_pause_campaign':
      return { content: [{ type: 'text', text: JSON.stringify(await client.pauseCampaign((args as any)?.campaignId), null, 2) }] };
Behavior1/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether pausing is reversible, requires specific permissions, affects ongoing emails, or has side effects. The single word 'Wstrzymuje' (Pauses) lacks context on outcomes or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While concise with one word, the description is under-specified rather than efficiently structured. It lacks front-loaded critical information and fails to earn its place by providing insufficient value, making it ineffective despite brevity.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what pausing entails, potential impacts, success criteria, or return values, leaving significant gaps in understanding for safe and correct usage.

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' clearly documented in the schema as 'ID kampanii' (campaign ID). The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema handles parameter documentation adequately.

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 'Wstrzymuje kampanię' (Pauses a campaign) is a tautology that restates the tool name 'fluentcrm_pause_campaign' without adding specificity. It doesn't clarify what 'pause' means operationally or distinguish it from sibling tools like 'fluentcrm_resume_campaign' or 'fluentcrm_delete_campaign'.

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. The description doesn't mention prerequisites (e.g., campaign must be active), exclusions, or relationships to sibling tools like 'fluentcrm_resume_campaign' for resuming or 'fluentcrm_delete_campaign' for removal.

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