Skip to main content
Glama

fluentcrm_create_webhook

Create webhooks in FluentCRM to automate data flow between your marketing platform and external applications or services.

Instructions

Tworzy nowy webhook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNazwa webhook
urlYesURL webhook
statusYes
tagsNo
listsNo

Implementation Reference

  • Core handler function that implements the tool logic by making a POST request to FluentCRM's /webhook endpoint.
    async createWebhook(data: {
      name: string;
      status: 'pending' | 'subscribed';
      url: string;
      tags?: number[];
      lists?: number[];
    }) {
      const response = await this.apiClient.post('/webhook', data);
      return response.data;
    }
  • Tool registration in the MCP server's ListTools handler, defining name, description, and input schema.
    {
      name: 'fluentcrm_create_webhook',
      description: 'Tworzy nowy webhook',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Nazwa webhook' },
          url: { type: 'string', description: 'URL webhook' },
          status: { type: 'string', enum: ['pending', 'subscribed'] },
          tags: { type: 'array', items: { type: 'number' } },
          lists: { type: 'array', items: { type: 'number' } },
        },
        required: ['name', 'url', 'status'],
      },
    },
  • MCP CallToolRequestSchema dispatch case that invokes the createWebhook method on the FluentCRM client instance.
    case 'fluentcrm_create_webhook':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createWebhook(args as any), null, 2) }] };
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'creates' which implies a write/mutation operation, but doesn't disclose any behavioral traits such as permissions required, whether the creation is idempotent, what happens on duplicate URLs, or what the response looks like (since no output schema exists). This is inadequate 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 extremely concise with just three words in Polish ('Tworzy nowy webhook'), which is appropriately sized for its limited content. It's front-loaded with the core action, though this brevity comes at the cost of completeness. No wasted words.

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?

Given the tool's complexity (5 parameters, mutation operation), lack of annotations, and no output schema, the description is completely inadequate. It doesn't explain what a webhook does in this context, how it integrates with FluentCRM, what events it triggers, or provide any operational details. For a creation tool with multiple parameters, this leaves critical gaps.

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

Parameters1/5

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

Schema description coverage is only 40% (2 out of 5 parameters have descriptions: 'name' and 'url'), and the description adds no information about parameters beyond what's in the schema. It doesn't explain what 'tags' and 'lists' arrays refer to, the meaning of 'status' enum values, or provide any context for required fields. With low coverage and no compensation in the description, this fails to add meaningful semantics.

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 'Tworzy nowy webhook' (Creates a new webhook) is a tautology that essentially restates the tool name 'fluentcrm_create_webhook' in Polish. It doesn't specify what kind of webhook (e.g., for what events or system) or provide any distinguishing details from sibling tools like 'fluentcrm_list_webhooks'. The purpose is clear at a basic level 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 Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when webhooks are appropriate compared to other methods, or how it relates to sibling tools like 'fluentcrm_list_webhooks' for viewing existing webhooks. There's complete absence of usage context.

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