Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

salvar_perfil_usuario

Create or update a user access profile in Ploomes CRM, setting permissions for modules, entities, and extra properties to control visibility and actions.

Instructions

    Criar ou atualizar um perfil de usuário (nível de acesso) no Ploomes CRM.

    Passe o ID para atualizar um perfil existente.

    Observações:
        1. Use buscar_perfis_usuario para obter o ID de um perfil existente e
           para conferir os módulos/permissões já configurados.
        2. Os campos *_visualizar / *_editar / *_excluir (Contatos, Negócios,
           Leads) são inteiros que representam o escopo de visibilidade
           (ex.: todos os registros da empresa, só da equipe, ou só os
           próprios). O código exato de cada escopo não está documentado de
           forma confiável — antes de usar em produção, confirme o valor
           comparando com um perfil equivalente já criado manualmente no
           admin do Ploomes (via buscar_perfis_usuario) ou testando numa
           conta de sandbox.
        3. Depois de criar o perfil, use salvar_usuario(perfil_id=...) para
           vincular usuários a ele.
        4. Este tool cobre as permissões gerais (CRUD por entidade). As
           permissões específicas (visibilidade de aba/funil/modelo/campo
           por usuário ou equipe) são configuradas no próprio objeto (aba,
           funil, modelo), não no perfil.
        5. permissoes_extra aceita qualquer propriedade nativa de UserProfile
           não listada explicitamente acima (ex.: TeamsView, EmailsView,
           GoalsDealsCreate, HomeMessagesCreate, LogsViewPermission).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nomeYes
chat_moduloNo
leads_criarNo
campos_criarNo
leads_editarNo
leads_moduloNo
metas_moduloNo
administradorNo
campos_editarNo
emails_moduloNo
leads_excluirNo
pedidos_criarNo
campos_excluirNo
contatos_criarNo
exportar_excelNo
importar_excelNo
negocios_criarNo
pedidos_editarNo
pedidos_moduloNo
tarefas_moduloNo
contatos_editarNo
contatos_moduloNo
negocios_editarNo
negocios_moduloNo
pedidos_excluirNo
propostas_criarNo
contatos_excluirNo
documentos_criarNo
leads_visualizarNo
negocios_excluirNo
negocios_reabrirNo
permissoes_extraNo
propostas_editarNo
propostas_moduloNo
biblioteca_moduloNo
documentos_editarNo
documentos_moduloNo
propostas_excluirNo
relatorios_moduloNo
documentos_excluirNo
contatos_visualizarNo
negocios_visualizarNo
pedidos_compartilharNo
produtos_administrarNo
negocios_ganhar_perderNo
propostas_compartilharNo
documentos_compartilharNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses create/update behavior, that passing ID updates existing, that integer visibility fields are not reliably documented, and that extra permissions can be passed via permissoes_extra. However, it does not describe success/error response or potential side effects.

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?

Description is front-loaded with main purpose, followed by structured observations (numbered list). Appropriate length for a tool with many parameters, though slightly verbose. No wasted sentences.

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?

No output schema exists, so description should cover return values. It omits what the tool returns (e.g., created/updated profile object). Also missing authentication or admin privilege requirements. However, it provides sufficient context for usage with siblings and sandbox testing.

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 has 48 parameters with 0% coverage from description. Description compensates by explaining the pattern for *_visualizar/*_editar/*_excluir fields (integers for visibility scope) and the flexible permissoes_extra parameter. This adds meaning for key parameters but does not describe all 48 individually, leaving gap.

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 explicitly states 'Criar ou atualizar um perfil de usuário (nível de acesso) no Ploomes CRM.' It distinguishes from sibling tool buscar_perfis_usuario by specifying its role in obtaining IDs and checking existing permissions. The purpose is specific and clear.

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?

Provides clear when-to-use (create/update profiles), when-to-use-alternatives (buscar_perfis_usuario for reading, other tools for specific permissions like tab/funnel/model visibility), and includes practical notes on testing integer values in sandbox. Explicit and actionable.

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