Skip to main content
Glama

fluentcrm_get_smart_link

Retrieve specific smart link details from FluentCRM marketing automation by providing the smart link ID.

Instructions

Pobiera szczegóły konkretnego Smart Link

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
smartLinkIdYesID Smart Link

Implementation Reference

  • Core implementation of the tool logic: calls FluentCRM API to retrieve smart link details by ID, handles 404 gracefully since the endpoint may not exist yet.
    async getSmartLink(smartLinkId: number) {
      try {
        const response = await this.apiClient.get(`/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: "Use FluentCRM admin panel to view Smart Link details"
          };
        }
        throw error;
      }
    }
  • Tool registration in MCP server's listTools handler, defining name, description, and input schema.
    {
      name: 'fluentcrm_get_smart_link',
      description: 'Pobiera szczegóły konkretnego Smart Link',
      inputSchema: {
        type: 'object',
        properties: {
          smartLinkId: { type: 'number', description: 'ID Smart Link' },
        },
        required: ['smartLinkId'],
      },
    },
  • Input schema validation: requires smartLinkId as number.
    inputSchema: {
      type: 'object',
      properties: {
        smartLinkId: { type: 'number', description: 'ID Smart Link' },
      },
      required: ['smartLinkId'],
    },
  • MCP server request handler switch case that invokes the tool implementation with the provided smartLinkId argument.
    case 'fluentcrm_get_smart_link':
      return { content: [{ type: 'text', text: JSON.stringify(await client.getSmartLink((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 the full burden. It states the action ('Pobiera' - retrieves) but doesn't disclose behavioral traits such as whether this is a read-only operation, what permissions are required, error handling, or the format of returned details. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what details are returned, potential errors, or usage context. For a tool that retrieves specific data, more information on the response format and behavioral aspects would be necessary for an agent to use it effectively.

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 schema description coverage is 100%, with the parameter 'smartLinkId' clearly documented as 'ID Smart Link'. The description adds no additional meaning beyond this, as it doesn't explain what a Smart Link ID is, where to find it, or its format. With high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter information.

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

Purpose4/5

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

The description clearly states the verb ('Pobiera' - retrieves/fetches) and resource ('szczegóły konkretnego Smart Link' - details of a specific Smart Link), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'fluentcrm_list_smart_links' or 'fluentcrm_update_smart_link' beyond the 'specific' aspect, which is why it doesn't reach a perfect score.

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 is provided on when to use this tool versus alternatives. The description mentions 'specific Smart Link' but doesn't clarify if this is for viewing details after listing, editing, or other contexts. There's no mention of prerequisites, alternatives like 'fluentcrm_list_smart_links', or exclusions.

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