Skip to main content
Glama

fluentcrm_create_campaign

Create email campaigns in FluentCRM by specifying title, subject, template, and recipient lists for targeted marketing communications.

Instructions

Tworzy nową kampanię email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTytuł kampanii
subjectYesTemat emaila
template_idNoID szablonu
recipient_listNoID list

Implementation Reference

  • The main handler function in FluentCRMClient class that implements the tool logic by making a POST request to the '/campaigns' endpoint with the input data.
    async createCampaign(data: any) {
      const response = await this.apiClient.post('/campaigns', data);
      return response.data;
    }
  • The MCP server request handler switch case that dispatches the tool call to the client.createCampaign method.
    case 'fluentcrm_create_campaign':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createCampaign(args as any), null, 2) }] };
  • Registers the tool in the MCP server's tools list, including name, description, and input schema.
      name: 'fluentcrm_create_campaign',
      description: 'Tworzy nową kampanię email',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Tytuł kampanii' },
          subject: { type: 'string', description: 'Temat emaila' },
          template_id: { type: 'number', description: 'ID szablonu' },
          recipient_list: { type: 'array', items: { type: 'number' }, description: 'ID list' },
        },
        required: ['title', 'subject'],
      },
    },
  • Defines the input schema for validating tool arguments: requires title and subject, optional template_id and recipient_list.
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Tytuł kampanii' },
        subject: { type: 'string', description: 'Temat emaila' },
        template_id: { type: 'number', description: 'ID szablonu' },
        recipient_list: { type: 'array', items: { type: 'number' }, description: 'ID list' },
      },
      required: ['title', 'subject'],
  • Instantiates the FluentCRMClient instance used by all tool handlers, configured with API credentials.
    const client = new FluentCRMClient(
      FLUENTCRM_API_URL,
      FLUENTCRM_API_USERNAME,
      FLUENTCRM_API_PASSWORD
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'creates' which implies a write operation, but doesn't cover critical aspects like permissions required, whether the campaign starts immediately or needs activation, what happens on failure, or if there are rate limits. For a creation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence in Polish that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded with the essential information, making it easy to parse quickly.

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

Completeness2/5

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

Given that this is a creation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after creation (e.g., returns a campaign ID, starts sending emails), doesn't mention dependencies on other tools (like needing existing templates or lists), and provides no behavioral context. For a tool that creates email campaigns—a potentially complex operation—more context is needed.

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?

The schema description coverage is 100%, with all 4 parameters well-documented in the input schema (title, subject, template_id, recipient_list). The description adds no additional parameter information beyond what's already in the schema. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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

Purpose4/5

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

The description 'Tworzy nową kampanię email' (Creates a new email campaign) clearly states the verb 'creates' and the resource 'email campaign', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'fluentcrm_create_automation' or 'fluentcrm_create_email_template', which also create different resources in the same system.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing templates or lists), exclusions, or relationships with sibling tools like 'fluentcrm_list_campaigns' or 'fluentcrm_delete_campaign'. The agent must infer usage from the tool name alone.

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