Skip to main content
Glama
Miguelgbastos

Kommo CRM MCP Server

get_companies

Retrieve a paginated list of companies from Kommo CRM, specifying the number of results per page and the page number for efficient data management.

Instructions

Get list of companies from Kommo CRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of companies to return (max 250)
pageNoPage number for pagination

Implementation Reference

  • Registration of the get_companies tool in the MCP tools/list response, including input schema
      name: 'get_companies',
          description: 'Obter lista de empresas do Kommo CRM',
      inputSchema: {
        type: 'object',
        properties: {
              limit: { type: 'number', description: 'Número máximo de empresas (padrão: 1000)' },
              page: { type: 'number', description: 'Página para paginação (padrão: 1)' }
            }
      }
    },
  • Input schema definition for get_companies tool
      inputSchema: {
        type: 'object',
        properties: {
              limit: { type: 'number', description: 'Número máximo de empresas (padrão: 1000)' },
              page: { type: 'number', description: 'Página para paginação (padrão: 1)' }
            }
      }
    },
  • Handler implementation for get_companies: calls KommoAPI.getCompanies and returns JSON stringified data
    case 'get_companies':
      const companiesLimit = args?.limit || 1000;
      const companiesPage = args?.page || 1;
      const companiesData = await kommoAPI.getCompanies({ limit: companiesLimit, page: companiesPage });
      
      result = {
        content: [
          {
            type: 'text',
            text: JSON.stringify(companiesData, null, 2)
          }
        ]
      };
      break;
  • KommoAPI.getCompanies method: API client call to fetch companies from Kommo CRM
    async getCompanies(params?: any): Promise<{ _embedded: { companies: KommoCompany[] } }> {
      const response = await this.client.get('/api/v4/companies', { params });
      return response.data;
    }
  • Type definition for KommoCompany, used in the return type of getCompanies
    export interface KommoCompany {
      id: number;
      name: string;
      responsible_user_id: number;
      created_by: number;
      created_at: number;
      updated_at: number;
      custom_fields_values?: any[];
      tags?: string[];
      leads?: KommoLead[];
      contacts?: KommoContact[];
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Get list' which implies a read operation, but doesn't cover important aspects like whether it requires authentication, rate limits, pagination behavior beyond the schema parameters, or what the return format looks like (e.g., array of company objects).

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 that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded with the essential information.

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?

For a list-retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what data is returned (company fields, structure), how pagination works in practice, or any constraints beyond the schema parameters. Given the complexity of CRM data and lack of structured output information, more context is needed.

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?

The schema description coverage is 100%, with both parameters ('limit' and 'page') well-documented in the schema itself. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for adequate coverage without adding value.

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 ('list of companies from Kommo CRM'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_contacts' or 'get_leads' beyond specifying the resource type, which is why it doesn't reach a perfect score.

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_contacts' or 'get_leads'. The description only states what it does, not when it's appropriate or what distinguishes it from other list-retrieval tools in the CRM 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

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