Skip to main content
Glama

fluentcrm_list_smart_links

Retrieve and search Smart Links from FluentCRM marketing automation to manage tracked URLs and campaign links within your WordPress plugin.

Instructions

Pobiera listę Smart Links z FluentCRM (może nie być dostępne w obecnej wersji)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNumer strony
searchNoSzukaj Smart Link

Implementation Reference

  • Core handler function in FluentCRMClient that attempts to fetch smart links from '/smart-links' endpoint and provides fallback message if not available (404).
    async listSmartLinks(params: any = {}) {
      // Try to get smart links - this might not work until FluentCRM adds the endpoint
      try {
        const response = await this.apiClient.get('/smart-links', { params });
        return response.data;
      } catch (error: any) {
        // If endpoint doesn't exist, return helpful message
        if (error.response?.status === 404) {
          return {
            success: false,
            message: "Smart Links API endpoint not available yet in FluentCRM",
            suggestion: "Use FluentCRM admin panel to manage Smart Links manually",
            available_endpoints: [
              "FluentCRM → Smart Links (admin panel)",
              "Custom WordPress hooks for Smart Links"
            ]
          };
        }
        throw error;
      }
    }
  • Tool registration in the MCP server's tools list, including name, description, and input schema.
      name: 'fluentcrm_list_smart_links',
      description: 'Pobiera listę Smart Links z FluentCRM (może nie być dostępne w obecnej wersji)',
      inputSchema: {
        type: 'object',
        properties: {
          page: { type: 'number', description: 'Numer strony' },
          search: { type: 'string', description: 'Szukaj Smart Link' },
        },
      },
    },
  • MCP server request handler case that delegates execution to client.listSmartLinks and formats response.
    case 'fluentcrm_list_smart_links':
      return { content: [{ type: 'text', text: JSON.stringify(await client.listSmartLinks(args || {}), null, 2) }] };
  • Input schema for the tool defining optional page and search parameters.
    inputSchema: {
      type: 'object',
      properties: {
        page: { type: 'number', description: 'Numer strony' },
        search: { type: 'string', description: 'Szukaj Smart Link' },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read operation ('Pobiera listę') but lacks details on permissions, rate limits, pagination, or error handling. The note about potential unavailability adds some context but is vague, failing to fully compensate for the absence of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with a single sentence stating the purpose, followed by a brief note. It is front-loaded with the main action, though the note about availability could be more precise. Overall, it avoids unnecessary verbosity and is structurally sound.

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 moderate complexity (list retrieval with two parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, output format, and usage context, leaving gaps that could hinder effective tool selection and invocation.

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 input schema has 100% description coverage, clearly documenting both parameters ('page' and 'search'). The description does not add any meaning beyond the schema, such as explaining how pagination works or search functionality specifics. According to the rules, with high schema coverage, the baseline score is 3.

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 the purpose ('Pobiera listę Smart Links z FluentCRM') which translates to 'Retrieves a list of Smart Links from FluentCRM', providing a clear verb and resource. However, it does not distinguish this tool from other list tools like fluentcrm_list_automations or fluentcrm_list_campaigns, and includes an ambiguous note about availability ('może nie być dostępne w obecnej wersji'), which slightly reduces clarity.

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 explicit guidance is provided on when to use this tool versus alternatives. The description mentions potential unavailability but does not specify conditions, prerequisites, or compare it to similar tools like fluentcrm_get_smart_link or fluentcrm_list_contacts, leaving usage context implied at best.

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