Skip to main content
Glama

fluentcrm_create_automation

Create new marketing automation workflows in FluentCRM by defining triggers and titles to automate customer engagement and communication processes.

Instructions

Tworzy nową automatyzację

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNazwa automatyzacji
descriptionNo
triggerYesTyp triggera

Implementation Reference

  • The core handler function in FluentCRMClient class that implements the tool logic by making a POST request to the '/funnels' endpoint to create a new automation.
    async createAutomation(data: any) {
      const response = await this.apiClient.post('/funnels', data);
      return response.data;
    }
  • Tool registration in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'fluentcrm_create_automation',
      description: 'Tworzy nową automatyzację',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Nazwa automatyzacji' },
          description: { type: 'string' },
          trigger: { type: 'string', description: 'Typ triggera' },
        },
        required: ['title', 'trigger'],
      },
    },
  • Input schema definition specifying required parameters: title and trigger, with optional description.
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Nazwa automatyzacji' },
        description: { type: 'string' },
        trigger: { type: 'string', description: 'Typ triggera' },
      },
      required: ['title', 'trigger'],
    },
  • Dispatch handler in the MCP request handler switch statement that calls the client.createAutomation method.
    case 'fluentcrm_create_automation':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createAutomation(args as any), null, 2) }] };
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. It only states the action ('creates') without disclosing behavioral traits like permissions required, whether it's idempotent, what happens on failure, or what the output looks like. For a mutation tool with zero annotation coverage, this is inadequate.

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

Conciseness3/5

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

The description is a single, concise sentence in Polish, which is efficient but under-specified. While it's front-loaded with the core action, it lacks necessary detail, making brevity come at the cost of clarity rather than being a virtue.

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 tool's complexity (creating an automation with 3 parameters), lack of annotations, no output schema, and incomplete schema coverage, the description is severely inadequate. It doesn't address what an automation is, how it behaves, or what to expect after creation, leaving critical gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67% (2 of 3 parameters have descriptions). The description adds no parameter information beyond what's in the schema—it doesn't explain what 'automation' entails, provide examples for 'trigger' types, or clarify the purpose of the 'description' field. With low coverage, it fails to compensate.

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 'Tworzy nową automatyzację' (Creates a new automation) restates the tool name 'fluentcrm_create_automation' in Polish, making it tautological. It doesn't specify what 'automation' means in this context or differentiate it from sibling tools like 'fluentcrm_create_campaign' or 'fluentcrm_create_webhook', which also create resources.

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, dependencies, or when other tools like 'fluentcrm_list_automations' might be more appropriate. The description offers no context for usage decisions.

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