Skip to main content
Glama

fluentcrm_list_campaigns

Retrieve email campaign lists from FluentCRM to manage marketing automation, with options to search and paginate results.

Instructions

Pobiera listę kampanii email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
searchNo

Implementation Reference

  • MCP server request handler case for 'fluentcrm_list_campaigns' tool. Receives arguments, calls client.listCampaigns, and formats response as MCP content.
    case 'fluentcrm_list_campaigns':
      return { content: [{ type: 'text', text: JSON.stringify(await client.listCampaigns(args || {}), null, 2) }] };
  • FluentCRMClient method implementing the core logic: GET request to /campaigns API endpoint with optional params (page, search), returns API response data.
    async listCampaigns(params: any = {}) {
      const response = await this.apiClient.get('/campaigns', { params });
      return response.data;
    }
  • Registration of the tool in MCP server's tools list, defining name, description, and input schema for pagination and search.
    {
      name: 'fluentcrm_list_campaigns',
      description: 'Pobiera listę kampanii email',
      inputSchema: {
        type: 'object',
        properties: {
          page: { type: 'number' },
          search: { type: 'string' },
        },
      },
    },
  • Input schema defining optional 'page' (number) and 'search' (string) parameters for listing campaigns.
    inputSchema: {
      type: 'object',
      properties: {
        page: { type: 'number' },
        search: { type: 'string' },
      },
    },
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. While 'retrieves' implies a read-only operation, it doesn't specify whether this requires authentication, what format the list returns in, whether results are paginated, or any rate limits. The description is too minimal for a tool with parameters.

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 extremely concise - a single phrase that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it front-loaded and efficient.

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 operation with 2 parameters and no output schema, the description is insufficient. It doesn't explain what the parameters do, what format the results come in, or any behavioral constraints. With no annotations and minimal description, this leaves significant gaps for the agent to understand how to properly use the tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but doesn't mention parameters at all. The tool has 2 parameters (page and search) that are completely undocumented in both schema and description, leaving the agent with no guidance on how to use pagination or search functionality.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Pobiera listę kampanii email' which translates to 'Retrieves a list of email campaigns' - this clearly indicates the verb (retrieves) and resource (email campaigns). However, it doesn't distinguish this tool from other list tools like fluentcrm_list_contacts or fluentcrm_list_automations beyond specifying the resource type.

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. With sibling tools like fluentcrm_get_contact (for single items) and fluentcrm_list_contacts (for lists of a different resource), there's no indication of when to choose list_campaigns over other list operations or when to use it versus get operations for campaigns.

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