Skip to main content
Glama
netflyapp

FluentCRM MCP Server

by netflyapp
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

fluentcrm_create_tag

Create new tags in FluentCRM to organize and segment contacts for targeted marketing automation workflows.

Instructions

Tworzy nowy tag w FluentCRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNazwa tagu (np. "AW-progress-75")
slugNoSlug tagu (np. "aw-progress-75")
descriptionNoOpis tagu

Implementation Reference

  • src/fluentcrm-mcp-server.ts:109-116 (handler)
    Core handler function in FluentCRMClient that executes the tool logic: POST request to /tags endpoint with title, slug, description.
    async createTag(data: {
  title: string;
  slug?: string;
  description?: string;
}) {
  const response = await this.apiClient.post('/tags', data);
  return response.data;
}
  • src/fluentcrm-mcp-server.ts:959-960 (handler)
    MCP server request handler dispatch case that invokes the client.createTag method with tool arguments.
    case 'fluentcrm_create_tag':
  return { content: [{ type: 'text', text: JSON.stringify(await client.createTag(args as any), null, 2) }] };
  • src/fluentcrm-mcp-server.ts:577-589 (registration)
    Tool registration in the MCP tools list, including name, description, and input schema.
    {
  name: 'fluentcrm_create_tag',
  description: 'Tworzy nowy tag w FluentCRM',
  inputSchema: {
    type: 'object',
    properties: {
      title: { type: 'string', description: 'Nazwa tagu (np. "AW-progress-75")' },
      slug: { type: 'string', description: 'Slug tagu (np. "aw-progress-75")' },
      description: { type: 'string', description: 'Opis tagu' },
    },
    required: ['title'],
  },
},
  • src/fluentcrm-mcp-server.ts:580-588 (schema)
    Input schema definition for validating tool arguments: requires title, optional slug and description.
    inputSchema: {
  type: 'object',
  properties: {
    title: { type: 'string', description: 'Nazwa tagu (np. "AW-progress-75")' },
    slug: { type: 'string', description: 'Slug tagu (np. "aw-progress-75")' },
    description: { type: 'string', description: 'Opis tagu' },
  },
  required: ['title'],
},

Tool Definition Quality

C2.9/5.0
Behavior2/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 states it creates a new tag, implying a write operation, but doesn't disclose behavioral traits like whether it requires authentication, what happens on duplicate tag names (e.g., error or update), rate limits, or what the return value might be (e.g., tag ID or success confirmation). This leaves significant gaps for an agent to use it correctly.

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 ('Tworzy nowy tag w FluentCRM') that directly states the purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste.

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 the tool's complexity (a write operation with 3 parameters) and lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, error handling, or return values, which are crucial for an agent to invoke this tool effectively in a real-world context.

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 all three parameters (title, slug, description) well-documented in the schema. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 nowy tag w FluentCRM' clearly states the action ('tworzy' - creates) and resource ('nowy tag' - new tag) in FluentCRM. It's specific about creating a tag rather than listing or deleting tags, but it doesn't explicitly differentiate from sibling tools like fluentcrm_delete_tag or fluentcrm_list_tags beyond the verb choice.

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 admin permissions), when not to use it (e.g., if a tag already exists), or refer to related tools like fluentcrm_list_tags for checking existing tags or fluentcrm_attach_tag_to_contact for applying tags.

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