Skip to main content
Glama

fluentcrm_update_contact

Update contact information in FluentCRM marketing automation by modifying fields like name and phone number using the contact's ID.

Instructions

Aktualizuje dane kontaktu

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriberIdYesID kontaktu
first_nameNo
last_nameNo
phoneNo

Implementation Reference

  • MCP tool handler switch case that executes the tool by calling FluentCRMClient.updateContact with subscriberId and the provided arguments, returning JSON stringified response.
    case 'fluentcrm_update_contact':
      return { content: [{ type: 'text', text: JSON.stringify(await client.updateContact((args as any)?.subscriberId, args as any), null, 2) }] };
  • Input schema definition for the tool, specifying parameters like subscriberId (required), first_name, last_name, phone.
    inputSchema: {
      type: 'object',
      properties: {
        subscriberId: { type: 'number', description: 'ID kontaktu' },
        first_name: { type: 'string' },
        last_name: { type: 'string' },
        phone: { type: 'string' },
      },
      required: ['subscriberId'],
    },
  • Tool registration in the ListTools response, defining name, description, and input schema.
    {
      name: 'fluentcrm_update_contact',
      description: 'Aktualizuje dane kontaktu',
      inputSchema: {
        type: 'object',
        properties: {
          subscriberId: { type: 'number', description: 'ID kontaktu' },
          first_name: { type: 'string' },
          last_name: { type: 'string' },
          phone: { type: 'string' },
        },
        required: ['subscriberId'],
      },
    },
  • FluentCRMClient helper method that performs the actual API update via PUT request to /subscribers/{subscriberId} endpoint.
    async updateContact(subscriberId: number, data: any) {
      const response = await this.apiClient.put(`/subscribers/${subscriberId}`, data);
      return response.data;
    }
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 'updates' which implies mutation, but doesn't disclose behavioral traits like required permissions, whether changes are reversible, error handling, or rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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 in Polish ('Aktualizuje dane kontaktu'), which is appropriately sized and front-loaded. There's zero waste, making it highly concise and well-structured for its limited content.

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 tool's complexity as a mutation tool with 4 parameters, low schema coverage (25%), no annotations, and no output schema, the description is incomplete. It lacks details on behavior, parameter meanings, usage context, and expected outcomes, making it inadequate for effective tool selection and invocation.

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?

Schema description coverage is low at 25%, with only 'subscriberId' documented. The description adds no parameter semantics beyond the schema—it doesn't explain what 'first_name', 'last_name', or 'phone' represent, their formats, or constraints. This fails to compensate for the coverage gap.

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 'Aktualizuje dane kontaktu' (Updates contact data) states the verb 'updates' and resource 'contact data', providing a basic purpose. However, it's vague about what specific data can be updated and doesn't differentiate from sibling tools like 'fluentcrm_update_smart_link' or 'fluentcrm_get_contact'. It's adequate but lacks specificity.

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. For example, it doesn't mention using 'fluentcrm_create_contact' for new contacts or 'fluentcrm_get_contact' to retrieve before updating. The description implies usage for updating existing contacts but offers no explicit context 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