Skip to main content
Glama

fluentcrm_delete_list

Delete a contact list from FluentCRM marketing automation by specifying the list ID to remove it from your WordPress plugin.

Instructions

Usuwa listę z FluentCRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID listy

Implementation Reference

  • Handler for fluentcrm_delete_list tool: extracts listId from arguments and calls client.deleteList to delete the list via FluentCRM API.
    case 'fluentcrm_delete_list':
      return { content: [{ type: 'text', text: JSON.stringify(await client.deleteList((args as any)?.listId), null, 2) }] };
  • Registers the fluentcrm_delete_list tool in the MCP server's tool list, including name, description, and input schema.
    {
      name: 'fluentcrm_delete_list',
      description: 'Usuwa listę z FluentCRM',
      inputSchema: {
        type: 'object',
        properties: {
          listId: { type: 'number', description: 'ID listy' },
        },
        required: ['listId'],
      },
    },
  • FluentCRMClient helper method that performs the actual API deletion of a list by ID using DELETE /lists/{listId}.
    async deleteList(listId: number) {
      const response = await this.apiClient.delete(`/lists/${listId}`);
      return response.data;
    }
  • Input schema definition for fluentcrm_delete_list tool, requiring a numeric listId.
    inputSchema: {
      type: 'object',
      properties: {
        listId: { type: 'number', description: 'ID listy' },
      },
      required: ['listId'],
    },
Behavior1/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. It only states the action ('delete') without any details about permissions required, whether the deletion is permanent or reversible, rate limits, error conditions, or what the response looks like. This is inadequate for a destructive operation.

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, direct sentence in Polish that states the tool's 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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It lacks critical context like behavioral traits (e.g., permanence, permissions), usage guidelines, and output expectations. The high schema coverage for parameters is insufficient to compensate for these gaps.

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 the single parameter 'listId' documented as 'ID listy' (list ID). The description adds no additional meaning beyond what the schema provides, such as format examples or where to obtain the ID. With high schema coverage, the baseline is 3.

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 listę z FluentCRM' (Deletes a list from FluentCRM) clearly states the action (delete) and resource (list), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling deletion tools like fluentcrm_delete_campaign or fluentcrm_delete_tag, which would require a 5.

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 the list ID from fluentcrm_list_lists), consequences (e.g., what happens to contacts in the list), or when not to use it (e.g., for removing contacts from a list instead).

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