Skip to main content
Glama

fluentcrm_list_lists

Retrieve all contact lists from your FluentCRM marketing automation platform to manage audience segmentation and email campaigns.

Instructions

Pobiera wszystkie listy z FluentCRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the tool logic by fetching lists from FluentCRM API endpoint '/lists' using the apiClient.
    async listLists(params: any = {}) {
      const response = await this.apiClient.get('/lists', { params });
      return response.data;
    }
  • Input schema and metadata definition for the tool, indicating no required parameters.
      name: 'fluentcrm_list_lists',
      description: 'Pobiera wszystkie listy z FluentCRM',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registration and dispatch in the MCP CallToolRequestSchema handler switch statement, mapping tool name to the client.listLists execution.
    case 'fluentcrm_list_lists':
      return { content: [{ type: 'text', text: JSON.stringify(await client.listLists(), null, 2) }] };
  • Instantiation of the FluentCRMClient instance used by all tool handlers, including listLists.
    const client = new FluentCRMClient(
      FLUENTCRM_API_URL,
      FLUENTCRM_API_USERNAME,
      FLUENTCRM_API_PASSWORD
    );
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states it retrieves all lists but doesn't mention any behavioral traits like pagination, rate limits, authentication requirements, error conditions, or what 'all lists' entails (e.g., active/inactive, count limits). This leaves significant gaps for an agent to understand how the tool behaves.

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 unnecessary words or structural fluff. It's appropriately sized and front-loaded with the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate but incomplete. It states what the tool does but lacks behavioral context (e.g., return format, limitations) that would help an agent use it effectively. For a read-only list operation, more detail on output expectations would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it correctly doesn't mention any parameters, aligning with the schema. A baseline of 4 is appropriate for zero-parameter tools.

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 ('Pobiera' meaning 'Retrieves' or 'Gets') and the resource ('wszystkie listy z FluentCRM' meaning 'all lists from FluentCRM'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'fluentcrm_list_contacts' or 'fluentcrm_list_tags', which follow the same pattern for different resources.

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, when this tool is appropriate compared to other list-related tools (like 'fluentcrm_create_list' or 'fluentcrm_delete_list'), or any contextual constraints for its use.

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