Skip to main content
Glama

fluentcrm_create_contact

Create a new contact in FluentCRM marketing automation by providing email and optional contact details to build your customer database.

Instructions

Tworzy nowy kontakt w FluentCRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail kontaktu
first_nameNoImię
last_nameNoNazwisko
phoneNoNumer telefonu
address_line_1NoAdres
cityNoMiasto
countryNoKraj

Implementation Reference

  • MCP tool handler case that executes the fluentcrm_create_contact by calling FluentCRMClient.createContact with input arguments.
    case 'fluentcrm_create_contact':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createContact(args as any), null, 2) }] };
  • Input schema definition for the fluentcrm_create_contact tool, specifying parameters like email (required), names, phone, address fields.
    inputSchema: {
      type: 'object',
      properties: {
        email: { type: 'string', description: 'Email kontaktu' },
        first_name: { type: 'string', description: 'Imię' },
        last_name: { type: 'string', description: 'Nazwisko' },
        phone: { type: 'string', description: 'Numer telefonu' },
        address_line_1: { type: 'string', description: 'Adres' },
        city: { type: 'string', description: 'Miasto' },
        country: { type: 'string', description: 'Kraj' },
      },
      required: ['email'],
    },
  • Tool registration in the ListTools response, defining name, description, and input schema for fluentcrm_create_contact.
    {
      name: 'fluentcrm_create_contact',
      description: 'Tworzy nowy kontakt w FluentCRM',
      inputSchema: {
        type: 'object',
        properties: {
          email: { type: 'string', description: 'Email kontaktu' },
          first_name: { type: 'string', description: 'Imię' },
          last_name: { type: 'string', description: 'Nazwisko' },
          phone: { type: 'string', description: 'Numer telefonu' },
          address_line_1: { type: 'string', description: 'Adres' },
          city: { type: 'string', description: 'Miasto' },
          country: { type: 'string', description: 'Kraj' },
        },
        required: ['email'],
      },
    },
  • Core helper method in FluentCRMClient that creates a new contact by POSTing to the /subscribers API endpoint.
    async createContact(data: {
      email: string;
      first_name?: string;
      last_name?: string;
      phone?: string;
      address_line_1?: string;
      city?: string;
      state?: string;
      country?: string;
      postal_code?: string;
      [key: string]: any;
    }) {
      const response = await this.apiClient.post('/subscribers', data);
      return response.data;
    }
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 it's a creation operation, implying mutation, but doesn't describe what happens on success/failure, whether duplicates are allowed, what permissions are required, or what the response looks like. For a mutation 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 wasted words. It's appropriately sized and front-loaded with the core action, making it easy to understand at a glance.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation (e.g., returns a contact ID, triggers automations), error conditions, or how it integrates with sibling tools. Given the complexity of contact creation in a CRM context, more behavioral and contextual information 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 description adds no parameter information beyond what's already in the input schema, which has 100% coverage with clear descriptions for all 7 parameters. The baseline is 3 since the schema does the heavy lifting, but the description doesn't provide additional context like format requirements (e.g., email validation) or default behaviors for optional fields.

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 nowy kontakt' - Creates a new contact) and the resource ('w FluentCRM' - in FluentCRM), providing a specific verb+resource combination. However, it doesn't differentiate this tool from its sibling 'fluentcrm_update_contact' beyond the basic create vs. update distinction, missing an opportunity to clarify when to create versus update.

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., whether the contact must not already exist), when to use 'fluentcrm_update_contact' instead for existing contacts, or how it relates to other sibling tools like 'fluentcrm_attach_contact_to_list' for post-creation actions.

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