Skip to main content
Glama

fluentcrm_create_list

Create a new contact list in FluentCRM to organize subscribers for targeted email marketing campaigns.

Instructions

Tworzy nową listę w FluentCRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNazwa listy
slugNoSlug listy
descriptionNoOpis listy

Implementation Reference

  • Core implementation of the tool logic: creates a new list via POST to FluentCRM /lists API endpoint using the apiClient.
    async createList(data: {
      title: string;
      slug?: string;
      description?: string;
    }) {
      const response = await this.apiClient.post('/lists', data);
      return response.data;
  • Tool registration in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'fluentcrm_create_list',
      description: 'Tworzy nową listę w FluentCRM',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Nazwa listy' },
          slug: { type: 'string', description: 'Slug listy' },
          description: { type: 'string', description: 'Opis listy' },
        },
        required: ['title'],
      },
    },
  • MCP request handler switch case that delegates to the client.createList method and formats the response.
    case 'fluentcrm_create_list':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createList(args as any), null, 2) }] };
  • Input schema definition for the fluentcrm_create_list tool.
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Nazwa listy' },
        slug: { type: 'string', description: 'Slug listy' },
        description: { type: 'string', description: 'Opis listy' },
      },
      required: ['title'],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Tworzy nową listę' implies a write/mutation operation, the description doesn't disclose any behavioral traits such as required permissions, whether the operation is idempotent, what happens on duplicate titles/slugs, error conditions, or what the response contains. This leaves significant gaps for an agent to understand how to use this tool effectively.

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 that directly states the tool's purpose without any unnecessary words or structural issues. It's appropriately sized and front-loaded with the essential information.

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 mutation tool (creates a new list) with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions, error handling, or response format, nor does it provide usage context relative to sibling tools. The 100% schema coverage helps with parameters, but other critical information is missing for proper tool invocation.

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 three parameters (title, slug, description) clearly documented in the schema. 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 parameter information 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 clearly states the action ('Tworzy nową listę' - Creates a new list) and the resource ('w FluentCRM' - in FluentCRM), which is specific and unambiguous. However, it doesn't explicitly differentiate this tool from sibling tools like 'fluentcrm_list_lists' or 'fluentcrm_delete_list', which would be needed for a perfect score.

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. There are multiple sibling tools for managing lists (e.g., list_lists, delete_list), but the description doesn't mention any prerequisites, constraints, or when this creation tool is appropriate compared to other list-related operations.

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