Skip to main content
Glama

fluentcrm_list_webhooks

Retrieve webhooks configured in FluentCRM to monitor and manage automated data flows between your marketing platform and external applications.

Instructions

Pobiera webhooks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the fluentcrm_list_webhooks tool by calling the client's listWebhooks method and returning the JSON-formatted response.
    case 'fluentcrm_list_webhooks':
      return { content: [{ type: 'text', text: JSON.stringify(await client.listWebhooks(), null, 2) }] };
  • Registers the fluentcrm_list_webhooks tool in the MCP server's tools list, including its name, description, and empty input schema.
      name: 'fluentcrm_list_webhooks',
      description: 'Pobiera webhooks',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • FluentCRMClient helper method that performs the actual API GET request to '/webhooks' endpoint to retrieve the list of webhooks.
    async listWebhooks(params: any = {}) {
      const response = await this.apiClient.get('/webhooks', { params });
      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 the full burden. 'Pobiera' implies a read operation, but it doesn't disclose behavioral traits such as whether it returns all webhooks, supports pagination, requires authentication, or has rate limits. For a tool with zero annotation coverage, this leaves critical operational details unspecified.

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 extremely concise ('Pobiera webhooks'), which could be efficient but risks under-specification. It's front-loaded with the core action, but lacks any supporting context. While not verbose, it may be too brief to be fully helpful, earning a middle score.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It doesn't explain what the tool returns (e.g., list structure, error handling) or any behavioral nuances. For a retrieval tool, more context on output and usage is needed to be fully actionable.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 'Pobiera webhooks' (Polish for 'Retrieves webhooks') states the basic action but is minimal and lacks specificity. It doesn't clarify what 'webhooks' refers to (e.g., in FluentCRM context) or how they are retrieved (e.g., as a list, with filtering). Compared to siblings like 'fluentcrm_list_contacts' or 'fluentcrm_list_tags', it doesn't distinguish itself beyond the resource name, making it vague.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., after creating webhooks), or comparisons to other list tools (e.g., 'fluentcrm_list_automations'). The agent must infer usage from the name alone, which is insufficient for effective tool selection.

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