Skip to main content
Glama
Miguelgbastos

Kommo CRM MCP Server

get_lead_conversion_report

Generate lead conversion reports within a specified date range to track and analyze CRM performance, enabling data-driven insights for better pipeline management.

Instructions

Get lead conversion report for a date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_fromYesStart date (YYYY-MM-DD)
date_toYesEnd date (YYYY-MM-DD)

Implementation Reference

  • This is the core handler function that implements the logic for retrieving the lead conversion report from the Kommo API by making a GET request to '/api/v4/leads/reports' with report_type 'conversion'. It takes dateFrom and dateTo as parameters and returns the report data.
    async getLeadConversionReport(dateFrom: string, dateTo: string): Promise<any> {
      const response = await this.client.get('/api/v4/leads/reports', {
        params: {
          date_from: dateFrom,
          date_to: dateTo,
          report_type: 'conversion'
        }
      });
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, what permissions are needed, how data is returned, or any rate limits. The description merely states the action without behavioral context.

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 with zero waste. It's appropriately sized and front-loaded with the core purpose, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple 2-parameter input schema with full coverage and no output schema, the description is minimally adequate. However, as a reporting tool with no annotations, it should ideally explain what the report contains or its format to be more complete for agent use.

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%, so parameters are fully documented in the schema. The description adds no additional meaning beyond implying date-range filtering, which is already clear from the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Get' and resource 'lead conversion report', specifying it's for a date range. It distinguishes from siblings like get_lead_analytics or get_sales_report by focusing specifically on conversion metrics, though it doesn't explicitly contrast them.

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 like get_lead_analytics or get_sales_report. The description only states what it does without context about appropriate scenarios 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

Related 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/Miguelgbastos/Kommo-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server