Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_pipeline

Create or update a business pipeline in Ploomes CRM. Include stages, colors, and naming to define your sales funnel.

Instructions

    Criar ou atualizar um pipeline/funil de negócios no Ploomes CRM.

    Passe o ID para atualizar um pipeline existente.

    Observações:
        1. Use buscar_pipeline para obter o ID de um pipeline existente.
        2. etapas deve seguir o formato:
           [
             {
               "Name": "Prospecção",
               "Ordination": 1,
               "Color": "#4CAF50",
               "MaxDays": 7,
               "WinStage": false,
               "LoseStage": false
             },
             ...
           ]
        3. Ao criar um pipeline, as etapas são definidas junto com ele.
        4. Color da etapa deve ser um valor hexadecimal (ex: "#4CAF50").
        5. MaxDays define o número máximo de dias recomendados na etapa (pode ser null).
        6. WinStage e LoseStage marcam etapas de ganho e perda do negócio.
        7. icone_id: ID do ícone FontAwesome. Use buscar_icones_pipeline para listar opções.
        8. cor: Cor hexadecimal do pipeline (ex: "#2196F3").
        9. nome_singular / nome_plural / genero_id permitem configurar a nomenclatura do funil.
       10. tipo_funil aplica automaticamente ícone e nomenclatura padrão quando estes campos
           não forem informados manualmente.
       11. As duas visualizações (tabela e funil) são habilitadas por padrão ao criar.

    Tipos de funil aceitos em tipo_funil (exemplos):
        - aquisicao_clientes
        - marketing_leads
        - vendas_carteira
        - assistencia_tecnica
        - reativacao_clientes
        - pos_venda
        - onboarding_implantacao
        - cobranca
        - contratos
        - suporte
        - logistica
        - proposta_orcamento
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
corNo
nomeYes
etapasNo
icone_idNo
genero_idNo
tipo_funilNo
nome_pluralNo
nome_singularNo
habilitar_visualizacao_funilNo
habilitar_visualizacao_tabelaNo
Behavior4/5

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

No annotations provided, but description extensively covers behavioral details: format for etapas, hexadecimal color, MaxDays, WinStage/LoseStage, icone_id from buscar_icones_pipeline, nomenclature fields, tipo_funil defaults, and default visualizations. Missing permissions or rollback details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with numbered observations, front-loaded with purpose. Some redundancy and length could be trimmed, but overall clear and organized.

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

Completeness4/5

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

Given 11 parameters, no output schema, and no annotations, description covers most aspects including parameter details, defaults, and examples. Lacks error handling or return value, but complete for the tool's complexity.

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

Parameters5/5

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

Schema has 0% description coverage. Description compensates comprehensively: explains etapas structure, Color, MaxDays, WinStage/LoseStage, icone_id, cor, nome_singular/plural/genero_id, tipo_funil with accepted values, and visualizations defaults. Adds immense meaning beyond raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Criar ou atualizar um pipeline/funil de negócios' with specific verb+resource. Distinguishes from siblings like buscar_pipeline and excluir_pipeline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly says to pass ID for update and mentions using buscar_pipeline to obtain ID. Provides clear context but lacks explicit when-not-to-use guidance.

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/JoseAlmeida-Ploomes/ploomes-mcp'

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