Skip to main content
Glama

fluentcrm_update_smart_link

Modify a FluentCRM smart link's settings, including URL, tags, lists, and auto-login options, to update marketing automation behavior.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
smartLinkIdYesID Smart Link
titleNo
target_urlNo
apply_tagsNo
apply_listsNo
remove_tagsNo
remove_listsNo
auto_loginNo

Implementation Reference

  • Core implementation of the updateSmartLink method in FluentCRMClient class, which sends a PUT request to the FluentCRM API to update a Smart Link. Includes error handling for unavailable endpoints with a helpful fallback response.
    async updateSmartLink(smartLinkId: number, data: any) {
      try {
        const response = await this.apiClient.put(`/smart-links/${smartLinkId}`, 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: "Update Smart Link manually in FluentCRM admin panel"
          };
        }
        throw error;
      }
  • MCP server tool handler (switch case) that dispatches fluentcrm_update_smart_link tool calls to the FluentCRMClient.updateSmartLink method, formatting the response as MCP content.
    case 'fluentcrm_update_smart_link':
      return { content: [{ type: 'text', text: JSON.stringify(await client.updateSmartLink((args as any)?.smartLinkId, args as any), null, 2) }] };
  • Tool registration in the MCP server's listTools response, including the tool name, description, and input schema definition.
    {
      name: 'fluentcrm_update_smart_link',
      description: 'Aktualizuje Smart Link (może nie być dostępne w obecnej wersji)',
      inputSchema: {
        type: 'object',
        properties: {
          smartLinkId: { type: 'number', description: 'ID Smart Link' },
          title: { type: 'string' },
          target_url: { type: 'string' },
          apply_tags: { type: 'array', items: { type: 'number' } },
          apply_lists: { type: 'array', items: { type: 'number' } },
          remove_tags: { type: 'array', items: { type: 'number' } },
          remove_lists: { type: 'array', items: { type: 'number' } },
          auto_login: { type: 'boolean' },
        },
        required: ['smartLinkId'],
      },
Behavior1/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It mentions potential unavailability but doesn't explain what 'Smart Link' is, what permissions are required, whether this is a destructive operation, what happens on success/failure, or any rate limits. The description fails to disclose essential behavioral traits for an update operation.

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 (one sentence with a parenthetical), which could be efficient if it contained useful information. However, the content is mostly wasted on a tautology and vague warning. While structurally simple, it fails to deliver meaningful content in its concise form.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter update tool with no annotations, no output schema, and minimal schema documentation, the description is completely inadequate. It doesn't explain what a Smart Link is, what fields can be updated, what the operation does, what permissions are needed, or what to expect as a result. The vague availability warning adds confusion rather than completeness.

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?

With only 13% schema description coverage (only 'smartLinkId' has a description), the description provides no parameter information to compensate. It doesn't explain what 'apply_tags', 'remove_lists', 'auto_login', or other parameters mean, their expected formats, or how they interact. The description adds zero semantic value beyond the minimal schema documentation.

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

Purpose2/5

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

The description 'Aktualizuje Smart Link' (Updates Smart Link) is a tautology that restates the tool name 'fluentcrm_update_smart_link' in Polish. It adds no meaningful clarification about what 'Smart Link' refers to or what specific aspects are updated. The parenthetical note about potential unavailability 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 Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention sibling tools like 'fluentcrm_create_smart_link', 'fluentcrm_get_smart_link', 'fluentcrm_delete_smart_link', or 'fluentcrm_list_smart_links' that handle related operations. The warning about potential unavailability is vague and doesn't specify conditions or alternatives.

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