Skip to main content
Glama

fluentcrm_attach_contact_to_list

Assign a contact to specific mailing lists in FluentCRM to organize subscribers and target communications effectively.

Instructions

Przypisuje kontakt do listy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriberIdYesID kontaktu
listIdsYesLista ID list

Implementation Reference

  • Core handler function in FluentCRMClient that attaches a contact (subscriber) to specified lists by making a POST request to the FluentCRM REST API endpoint `/subscribers/{subscriberId}/lists`.
    async attachContactToList(subscriberId: number, listIds: number[]) {
      const response = await this.apiClient.post(
        `/subscribers/${subscriberId}/lists`,
        { lists: listIds }
      );
      return response.data;
    }
  • Tool registration in the MCP server's tools list, including the tool name, description, and input schema validation for subscriberId and listIds parameters.
    {
      name: 'fluentcrm_attach_contact_to_list',
      description: 'Przypisuje kontakt do listy',
      inputSchema: {
        type: 'object',
        properties: {
          subscriberId: { type: 'number', description: 'ID kontaktu' },
          listIds: { type: 'array', items: { type: 'number' }, description: 'Lista ID list' },
        },
        required: ['subscriberId', 'listIds'],
      },
    },
  • MCP server request handler switch case that processes the tool call by extracting arguments and invoking the FluentCRMClient's attachContactToList method, returning JSON-formatted response.
    case 'fluentcrm_attach_contact_to_list':
      return { content: [{ type: 'text', text: JSON.stringify(await client.attachContactToList((args as any)?.subscriberId, (args as any)?.listIds), null, 2) }] };
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 a mutation action ('assigns') but doesn't disclose behavioral traits like whether this is idempotent, what permissions are needed, error conditions, or what the tool returns. The description is too minimal for a mutation tool with zero annotation coverage.

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

Conciseness4/5

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

Extremely concise single sentence with zero waste. However, the Polish description mixed with English tool name creates a minor structural issue, and it could benefit from being front-loaded with more context given the mutation nature.

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 assignment, error scenarios, or relationship to sibling tools. The language inconsistency adds to the incompleteness.

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 both parameters clearly documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., format of IDs, whether listIds can be empty). Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose3/5

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

The description 'Przypisuje kontakt do listy' (Assigns contact to list) states a clear verb+resource action, but it's in Polish while the tool name is in English, creating potential confusion. It doesn't distinguish from sibling tools like 'fluentcrm_detach_contact_from_list' or explain the relationship to other contact/list operations.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., contact/list must exist), when to choose this over similar tools like 'fluentcrm_update_contact', or what happens if the contact is already on the list.

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