Skip to main content
Glama

fluentcrm_detach_contact_from_list

Remove a contact from specified lists in FluentCRM to manage audience segmentation and update contact relationships.

Instructions

Usuwa kontakt z listy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriberIdYesID kontaktu
listIdsYesLista ID list

Implementation Reference

  • MCP tool handler that executes the detach contact from list operation by calling the FluentCRMClient method with extracted arguments.
    case 'fluentcrm_detach_contact_from_list':
      return { content: [{ type: 'text', text: JSON.stringify(await client.detachContactFromList((args as any)?.subscriberId, (args as any)?.listIds), null, 2) }] };
  • Registers the tool in the MCP server's tool list, including name, description, and input schema.
    {
      name: 'fluentcrm_detach_contact_from_list',
      description: 'Usuwa kontakt z listy',
      inputSchema: {
        type: 'object',
        properties: {
          subscriberId: { type: 'number', description: 'ID kontaktu' },
          listIds: { type: 'array', items: { type: 'number' }, description: 'Lista ID list' },
        },
        required: ['subscriberId', 'listIds'],
      },
    },
  • Core implementation in FluentCRMClient: sends POST request to FluentCRM API endpoint to detach contact from specified lists.
    async detachContactFromList(subscriberId: number, listIds: number[]) {
      const response = await this.apiClient.post(
        `/subscribers/${subscriberId}/lists/detach`,
        { lists: listIds }
      );
      return response.data;
    }
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 the action ('usuwa' - removes) but doesn't disclose behavioral traits like whether this is a destructive operation (likely yes, but not confirmed), permission requirements, error handling (e.g., if contact/list doesn't exist), or side effects (e.g., impact on automation triggers). The description is minimal and lacks critical operational context.

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?

The description is a single, clear sentence ('Usuwa kontakt z listy') that directly states the purpose without unnecessary words. It's appropriately sized for a simple operation, though it could be slightly more informative without losing conciseness. No structural issues are present.

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 mutation operation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral aspects (e.g., destructiveness, error cases), usage context, and what to expect upon success or failure. For a tool that modifies data, this minimal description leaves significant gaps for an AI agent to understand its full implications.

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 ('subscriberId' and 'listIds') clearly documented in the schema. The description doesn't add any meaning beyond the schema (e.g., it doesn't explain parameter relationships or usage examples). With high schema coverage, the baseline score of 3 is appropriate as the schema already provides adequate parameter information.

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 'Usuwa kontakt z listy' (Removes contact from list) clearly states the action (remove/usuwa) and target (contact from list). It distinguishes from sibling tools like 'fluentcrm_attach_contact_to_list' by specifying removal rather than addition. However, it doesn't explicitly mention the resource (FluentCRM) or differentiate from 'fluentcrm_detach_tag_from_contact' beyond the list vs. tag distinction.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., contact must exist, list must exist), when not to use it (e.g., for bulk operations), or direct comparisons to siblings like 'fluentcrm_delete_contact' (which removes entirely) or 'fluentcrm_update_contact' (which might modify list membership).

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