Skip to main content
Glama

fluentcrm_generate_smart_link_shortcode

Generate shortcodes for FluentCRM Smart Links to embed trackable marketing links in WordPress content.

Instructions

Generuje shortcode dla Smart Link

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug Smart Link
linkTextNoTekst linku (opcjonalny)

Implementation Reference

  • Core implementation of the tool logic: generates FluentCRM smart link shortcode either as plain shortcode or wrapped in an anchor tag with optional link text.
    generateSmartLinkShortcode(slug: string, linkText?: string): string {
      if (linkText) {
        return `<a href="{{fc_smart_link slug='${slug}'}}">${linkText}</a>`;
      }
      return `{{fc_smart_link slug='${slug}'}}`;
    }
  • Input schema defining parameters: slug (required string) and optional linkText string.
    inputSchema: {
      type: 'object',
      properties: {
        slug: { type: 'string', description: 'Slug Smart Link' },
        linkText: { type: 'string', description: 'Tekst linku (opcjonalny)' },
      },
      required: ['slug'],
    },
  • Tool registration in the MCP server's tools list, specifying name, description, and input schema.
    {
      name: 'fluentcrm_generate_smart_link_shortcode',
      description: 'Generuje shortcode dla Smart Link',
      inputSchema: {
        type: 'object',
        properties: {
          slug: { type: 'string', description: 'Slug Smart Link' },
          linkText: { type: 'string', description: 'Tekst linku (opcjonalny)' },
        },
        required: ['slug'],
      },
    },
  • MCP server dispatch handler: switch case that calls the generateSmartLinkShortcode method and returns the result as JSON.
    case 'fluentcrm_generate_smart_link_shortcode':
      return { content: [{ type: 'text', text: JSON.stringify({ shortcode: client.generateSmartLinkShortcode((args as any)?.slug, (args as any)?.linkText) }, 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 of behavioral disclosure. It states the tool generates a shortcode, implying a read-only operation that outputs code, but doesn't specify if it's safe, what permissions are needed, if it has side effects (e.g., logging usage), or what the output format looks like (e.g., a string). This leaves significant gaps for an agent to understand 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.

Conciseness4/5

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

The description is a single, efficient sentence in Polish ('Generuje shortcode dla Smart Link'), which translates to 'Generates shortcode for Smart Link'. It's front-loaded and wastes no words, though it could benefit from more detail given the lack of annotations and output schema.

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 complexity (a tool that generates code-like output), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what a shortcode is, how it's used (e.g., in WordPress), what the output looks like, or any behavioral traits like safety or dependencies. This makes it inadequate for an agent to use the tool effectively without additional context.

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?

Schema description coverage is 100%, with clear descriptions for both parameters ('slug' and optional 'linkText'). The description doesn't add any meaning beyond the schema, such as explaining what a 'slug' represents or how the shortcode is used. With high schema coverage, the baseline score of 3 is appropriate, as the schema adequately documents parameters without extra help from the description.

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 tool generates a shortcode for a Smart Link, which provides a basic purpose (verb+resource). However, it's vague about what a 'Smart Link' is in this context and doesn't distinguish this tool from sibling tools like 'fluentcrm_create_smart_link' or 'fluentcrm_get_smart_link', leaving ambiguity about its specific role.

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. It doesn't mention prerequisites (e.g., needing an existing Smart Link), exclusions, or how it relates to sibling tools like 'fluentcrm_create_smart_link' for creating links or 'fluentcrm_get_smart_link' for retrieving link details.

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