Skip to main content

FluentCRM

#Bug Report

Issue:`list-contacts` tool ignores `page` and `tags` parameters

Issue: list-contacts tool ignores page and tags parameters

When calling the fluent-crm-list-contacts tool (fluent-crm MCP server), both the page and tags parameters appear to be ignored server-side.

Steps to reproduce:

  1. Call list-contacts with contact_type=lead, sort_by=last_activity, sort_type=DESC, per_page=50, page=1.
  2. Call it again with identical parameters except page=2.
  3. Both calls return the exact same 50 contacts, in the same order (verified by identical contact IDs across both responses). The response metadata does report "page":1 in both cases, even when page:2 was explicitly passed.

Second issue, same tool — tags filter:
Calling list-contacts with a tags parameter (e.g. tags: ["digigroei"] or tags: ["wachtlijst-lgd-lite"]) returns the full unfiltered contact list (total:521, identical to the count with no tag filter at all), rather than only contacts carrying that tag.

What does work:
The search parameter (full-text match on name/email/custom fields) filters and paginates correctly

Impact: With page and tags broken, it's impossible to retrieve more than the first 50 contacts (sorted by any criterion) or to segment contacts by tag through this tool — both are needed for behavior-based lead scoring across a full contact base of 521+.

  • 2 comments

Shahjahan Jewel

This is good timing. I am actually working on improving the MCP tools. on it.

Natascha Vantuykom

Shahjahan Jewel 

Feature Request: MCP tools for tag/automation analytics and reliable pagination

Context: Using an AI assistant connected via MCP to query FluentCRM contact data for lead scoring and list hygiene. The current MCP toolset only exposes list-contacts and get-contact, which limits what kind of analysis is possible.

Requested additions:

Fix list-contacts pagination and tag filtering — the page parameter currently has no effect (repeated calls with different page values return identical results), and the tags filter parameter returns the full unfiltered contact list instead of narrowing results. Both should filter/paginate as documented.

A list-tags tool — returns all tags with contact count per tag, and ideally the date of last use (i.e. last time the tag was applied to a contact). This would allow identifying stale/unused tags for cleanup.

A list-automations tool — returns all automations/funnels with their status (active/inactive) and last-triggered date, so unused automations can be identified and retired.

A get-contact-activity or similar tool — returns actual engagement history per contact (email opens, clicks, page visits) rather than an empty activity array, to support real behavior-based lead scoring rather than relying only on tags and last_activity timestamp.

Why this matters: Without these, an AI assistant can only work from the first page of contacts sorted by activity, and can't distinguish "engaged prospect" from "old tag nobody uses anymore" — both are common cleanup/segmentation tasks for lead nurturing.