Skip to main content
Glama

fluentcrm_delete_smart_link

Remove a smart link from FluentCRM marketing automation by specifying its ID. This action deletes the link from your WordPress plugin's campaign management system.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
smartLinkIdYesID Smart Link do usunięcia

Implementation Reference

  • Core handler function in FluentCRMClient that performs the DELETE request to the Smart Links API endpoint and handles potential 404 errors by returning a user-friendly message.
    async deleteSmartLink(smartLinkId: number) {
      try {
        const response = await this.apiClient.delete(`/smart-links/${smartLinkId}`);
        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: "Delete Smart Link manually in FluentCRM admin panel"
          };
        }
        throw error;
      }
    }
  • Input schema defining the required 'smartLinkId' parameter as a number.
    inputSchema: {
      type: 'object',
      properties: {
        smartLinkId: { type: 'number', description: 'ID Smart Link do usunięcia' },
      },
      required: ['smartLinkId'],
    },
  • Tool registration in the MCP server's tools list, including name, description, and input schema.
      name: 'fluentcrm_delete_smart_link',
      description: 'Usuwa Smart Link (może nie być dostępne w obecnej wersji)',
      inputSchema: {
        type: 'object',
        properties: {
          smartLinkId: { type: 'number', description: 'ID Smart Link do usunięcia' },
        },
        required: ['smartLinkId'],
      },
    },
  • MCP server request handler case that invokes the client.deleteSmartLink method and formats the response.
    case 'fluentcrm_delete_smart_link':
      return { content: [{ type: 'text', text: JSON.stringify(await client.deleteSmartLink((args as any)?.smartLinkId), null, 2) }] };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool deletes a Smart Link, implying a destructive mutation, but doesn't disclose critical behaviors: whether deletion is permanent/reversible, permission requirements, error handling, or side effects. The availability warning adds some context but is incomplete.

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

Conciseness3/5

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

The description is brief but not well-structured. The main action is clear upfront, but the parenthetical note about availability is distracting and reduces clarity. It could be more direct by separating concerns or omitting the speculative note.

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 destructive tool with no annotations and no output schema, the description is inadequate. It lacks details on what happens post-deletion, error cases, or confirmation of success. The availability warning doesn't compensate for missing behavioral context, making it incomplete for safe agent use.

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

Parameters4/5

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

Schema description coverage is 100% for the single parameter 'smartLinkId', so the schema fully documents it. The description adds no parameter information, which is acceptable given high coverage and zero parameters needing extra explanation. Baseline 4 applies as it doesn't detract from schema clarity.

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 'Usuwa Smart Link' (Deletes Smart Link) states the verb and resource, but it's vague about what a 'Smart Link' is and doesn't distinguish from sibling tools like 'fluentcrm_delete_campaign' or 'fluentcrm_delete_contact'. 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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing Smart Link ID), nor does it reference sibling tools like 'fluentcrm_get_smart_link' for verification or 'fluentcrm_list_smart_links' for 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