Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

criar_campos_em_massa_ia

Batch-creates custom fields in Ploomes CRM for AI-identified fields that are new, using position-based mapping to integrate with HTML markers.

Instructions

    Criar em massa, no Ploomes, os campos que a IA identificou (via
    identificar_campos_html_ia) e que ainda não existem no sistema.

    Endpoint: POST {PLOOMES_AI_BASE_URL}/bulk_fields_creation.

    IMPORTANTE — leia antes de usar:
        1. Envie APENAS os campos de identificar_campos_html_ia que
           vieram SEM Key (campos novos). Campos que já têm Key devem ser
           ignorados aqui — eles já existem, só precisam ser vinculados no
           HTML (use aplicar_campos_no_html_ia para isso).
        2. A correspondência entre os campos criados e os pontos
           marcados no HTML é feita por POSIÇÃO — ou seja, a ordem desta
           lista `campos` deve ser exatamente a mesma ordem em que esses
           campos (sem Key) apareceram na resposta de
           identificar_campos_html_ia. Não reordene.
        3. Depois de rodar esta ferramenta, use aplicar_campos_no_html_ia
           passando o html_com_ids original + a lista combinada (campos
           que já tinham Key + os recém-criados aqui) para obter o HTML
           final com <field key="..."> no lugar de <field id="N">.

    Parâmetros:
        campos: lista de objetos, cada um com:
            - Name (str, obrigatório): nome do campo.
            - TypeId (int, obrigatório): tipo do campo.
            - EntityId (int, obrigatório): entidade à qual o campo pertence.
            - PathId (int, opcional): caminho da entidade (de
              identificar_campos_html_ia).
            - Multiple (bool, opcional): se o campo é um bloco repetível.
        idioma: idioma do usuário (ex.: "pt-BR").

    Retorno: lista de campos criados, cada um agora com Key atribuída
    pelo sistema.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camposYes
idiomaNopt-BR
Behavior4/5

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

No annotations provided, but description discloses key behaviors: it's a write operation (POST), creates fields with Key, and requires maintaining order. Could mention rate limits or error handling but sufficient.

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?

Somewhat verbose but well-organized: purpose, endpoint, important notes, parameters, return. Important notes are essential. Minor redundancy possible but overall efficient.

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?

No output schema, but description explains return value as list of fields with Key. Lacks error handling details. However, given complexity and context with sibling tools, it's fairly complete.

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, but description fully documents each subfield of the campos array (Name, TypeId, EntityId, PathId, Multiple) and the idioma parameter with default. Adds meaning beyond 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 states it creates fields in bulk that were identified by identificar_campos_html_ia and do not exist yet. It distinguishes from sibling tools by specifying that fields with Key should be handled by aplicar_campos_no_html_ia.

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

Usage Guidelines5/5

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

Explicit numbered points tell when to use (only for fields without Key), when not to, and which alternative tool to use. Also emphasizes positional correspondence requirement.

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