Skip to main content
Glama

fluentcrm_list_contacts

Retrieve and manage contact lists from FluentCRM marketing automation with pagination and search capabilities for email or name queries.

Instructions

Pobiera listę wszystkich kontaktów z FluentCRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNumer strony (default: 1)
per_pageNoIlość rekordów na stronę (default: 10)
searchNoSzukaj po emailu/imieniu

Implementation Reference

  • MCP tool handler case that executes the tool by calling FluentCRMClient.listContacts with input args and returns JSON response.
    case 'fluentcrm_list_contacts':
      return { content: [{ type: 'text', text: JSON.stringify(await client.listContacts(args || {}), null, 2) }] };
  • Input schema defining optional parameters: page, per_page, search for listing contacts.
    inputSchema: {
      type: 'object',
      properties: {
        page: { type: 'number', description: 'Numer strony (default: 1)' },
        per_page: { type: 'number', description: 'Ilość rekordów na stronę (default: 10)' },
        search: { type: 'string', description: 'Szukaj po emailu/imieniu' },
      },
    },
  • Tool registration in ListTools response, including name, description, and input schema.
    {
      name: 'fluentcrm_list_contacts',
      description: 'Pobiera listę wszystkich kontaktów z FluentCRM',
      inputSchema: {
        type: 'object',
        properties: {
          page: { type: 'number', description: 'Numer strony (default: 1)' },
          per_page: { type: 'number', description: 'Ilość rekordów na stronę (default: 10)' },
          search: { type: 'string', description: 'Szukaj po emailu/imieniu' },
        },
      },
    },
  • Core implementation: Calls FluentCRM REST API /subscribers endpoint with params and returns the data.
    async listContacts(params: any = {}) {
      const response = await this.apiClient.get('/subscribers', { params });
      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 full burden but only states what the tool does without behavioral details. It doesn't disclose whether this is a read-only operation, if it requires authentication, potential rate limits, pagination behavior beyond parameters, or what format the returned list takes. For a list operation with zero annotation coverage, this is inadequate.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the core functionality, making it easy for an agent to parse quickly.

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 list retrieval tool with 3 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the returned data looks like, how pagination works beyond parameter names, or any constraints on the search functionality. The agent would need to guess about the response format and behavioral characteristics.

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%, so the schema already documents all three parameters with their purposes. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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' - retrieves) and resource ('listę wszystkich kontaktów z FluentCRM'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'fluentcrm_find_contact_by_email' or 'fluentcrm_get_contact', which suggests it retrieves all contacts rather than specific ones.

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. The description doesn't mention when to choose this over 'fluentcrm_find_contact_by_email' for email searches or 'fluentcrm_get_contact' for single contact retrieval, leaving the agent without context for tool selection.

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