Skip to main content
Glama

fluentcrm_create_smart_link

Create smart links in FluentCRM that track clicks and automatically manage contact tags and lists based on user interactions.

Instructions

Tworzy nowy Smart Link (może nie być dostępne w obecnej wersji)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNazwa Smart Link (np. "AW-Link-Webinar-Mail")
slugNoSlug (np. "aw-link-webinar-mail")
target_urlYesDocelowy URL
apply_tagsNoID tagów do dodania po kliknięciu
apply_listsNoID list do dodania po kliknięciu
remove_tagsNoID tagów do usunięcia po kliknięciu
remove_listsNoID list do usunięcia po kliknięciu
auto_loginNoCzy automatycznie logować użytkownika

Implementation Reference

  • Core handler function in FluentCRMClient that attempts to create a Smart Link via POST /smart-links, with graceful 404 handling indicating feature unavailability.
    async createSmartLink(data: {
      title: string;
      slug?: string;
      target_url: string;
      apply_tags?: number[];
      apply_lists?: number[];
      remove_tags?: number[];
      remove_lists?: number[];
      auto_login?: boolean;
    }) {
      try {
        const response = await this.apiClient.post('/smart-links', data);
        return response.data;
      } catch (error: any) {
        if (error.response?.status === 404) {
          return {
            success: false,
            message: "Smart Links API endpoint not available yet in FluentCRM",
            suggestion: "Create Smart Link manually in FluentCRM admin panel",
            recommended_data: data
          };
        }
        throw error;
      }
  • Tool registration in MCP server's tools list, including name, description, and detailed input schema.
      name: 'fluentcrm_create_smart_link',
      description: 'Tworzy nowy Smart Link (może nie być dostępne w obecnej wersji)',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Nazwa Smart Link (np. "AW-Link-Webinar-Mail")' },
          slug: { type: 'string', description: 'Slug (np. "aw-link-webinar-mail")' },
          target_url: { type: 'string', description: 'Docelowy URL' },
          apply_tags: { type: 'array', items: { type: 'number' }, description: 'ID tagów do dodania po kliknięciu' },
          apply_lists: { type: 'array', items: { type: 'number' }, description: 'ID list do dodania po kliknięciu' },
          remove_tags: { type: 'array', items: { type: 'number' }, description: 'ID tagów do usunięcia po kliknięciu' },
          remove_lists: { type: 'array', items: { type: 'number' }, description: 'ID list do usunięcia po kliknięciu' },
          auto_login: { type: 'boolean', description: 'Czy automatycznie logować użytkownika' },
        },
        required: ['title', 'target_url'],
      },
    },
  • MCP server request handler switch case that invokes the client.createSmartLink method with tool arguments.
    case 'fluentcrm_create_smart_link':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createSmartLink(args as any), null, 2) }] };
  • Input schema definition for the tool, specifying parameters and validation rules.
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Nazwa Smart Link (np. "AW-Link-Webinar-Mail")' },
        slug: { type: 'string', description: 'Slug (np. "aw-link-webinar-mail")' },
        target_url: { type: 'string', description: 'Docelowy URL' },
        apply_tags: { type: 'array', items: { type: 'number' }, description: 'ID tagów do dodania po kliknięciu' },
        apply_lists: { type: 'array', items: { type: 'number' }, description: 'ID list do dodania po kliknięciu' },
        remove_tags: { type: 'array', items: { type: 'number' }, description: 'ID tagów do usunięcia po kliknięciu' },
        remove_lists: { type: 'array', items: { type: 'number' }, description: 'ID list do usunięcia po kliknięciu' },
        auto_login: { type: 'boolean', description: 'Czy automatycznie logować użytkownika' },
      },
      required: ['title', 'target_url'],
    },
  • Supporting validation method for Smart Link data used by related tools.
    validateSmartLinkData(data: any): { valid: boolean; errors: string[] } {
      const errors: string[] = [];
      
      if (!data.title || typeof data.title !== 'string') {
        errors.push('Title is required and must be a string');
      }
      
      if (!data.target_url || typeof data.target_url !== 'string') {
        errors.push('Target URL is required and must be a string');
      }
      
      if (data.target_url && !data.target_url.startsWith('http')) {
        errors.push('Target URL must start with http:// or https://');
      }
      
      if (data.slug && !/^[a-z0-9-]+$/.test(data.slug)) {
        errors.push('Slug must contain only lowercase letters, numbers, and hyphens');
      }
      
      return {
        valid: errors.length === 0,
        errors
      };
    }
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. While 'Tworzy' (Creates) implies a write operation, the description fails to mention important behavioral aspects: what permissions are required, whether this is idempotent, what happens on failure, or what the response contains. The availability warning adds some context but doesn't address core behavioral traits.

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 extremely concise - just one sentence with a parenthetical note. While this is efficient, the availability warning feels like clutter that doesn't belong in the core description. The structure is front-loaded with the main action, but could be more informative.

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 creation tool with 8 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what a Smart Link is, what happens after creation, what the tool returns, or how it relates to other Smart Link operations. The availability warning doesn't compensate for these fundamental gaps in understanding the tool's role and behavior.

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?

With 100% schema description coverage, the schema already documents all 8 parameters thoroughly in Polish. The description adds no parameter information beyond what's in the schema, so it meets the baseline of 3 for high schema coverage situations where the structured data does the heavy lifting.

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 'Tworzy nowy Smart Link' (Creates a new Smart Link), which clearly indicates a creation action on a specific resource. However, it doesn't distinguish this tool from other creation tools like fluentcrm_create_contact or fluentcrm_create_campaign, and the parenthetical note about availability adds confusion rather than clarifying purpose.

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. There's no mention of prerequisites, when this tool is appropriate compared to other Smart Link tools (like fluentcrm_update_smart_link or fluentcrm_get_smart_link), or any context about what a 'Smart Link' actually is in the FluentCRM ecosystem.

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