Skip to main content
Glama
victorbenazzi

Ploomes MCP Server

List Fields

ploomes_fields_list
Read-onlyIdempotent

List custom fields in Ploomes CRM. Filter by entity ID to retrieve fields for contacts, deals, orders, quotes, products, tasks, or interactions.

Instructions

List custom fields configured in Ploomes CRM. Filter by EntityId to get fields for a specific entity. Known EntityId values: 1=Contact, 2=Deal, 4=Order, 7=Quote, 10=Product, 12=Task, 36=Interaction Record. Use ploomes_fields_entities_list for the complete mapping. Each field has a Key (used in OtherProperties when reading/writing custom field values), Name, and TypeId. Use ploomes_fields_types_list to understand which value property to use for each field type (e.g., StringValue, IntegerValue, DateTimeValue, BoolValue, BigStringValue, ObjectValueName). Use $expand=Entity,Type,OptionsTable to include related info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoOData $filter expression. E.g.: "EntityId eq 1" (Contact fields), "EntityId eq 2" (Deal fields), "EntityId eq 12" (Task fields), "TypeId eq 1", "Name eq 'Custom Field Name'"
selectNoFields to return. E.g.: "Id,Key,Name,EntityId,TypeId"
expandNoRelated entities to include. Available: "Entity", "SecondaryEntity", "Type", "OptionsTable". E.g.: "Entity,Type,OptionsTable"
orderbyNoSort expression. E.g.: "Name asc", "EntityId asc"
topNoMax items to return (default 100, max 300)
skipNoItems to skip for pagination
Behavior4/5

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

Annotations already indicate safe read operation; description adds context about Key usage in OtherProperties, $expand capabilities, and pagination parameters (top, skip). No contradictions with annotations.

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 concise and front-loaded with core purpose. Contains multiple useful pieces of information in a single paragraph. Slightly longer than minimal but each sentence adds value.

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?

Covers filtering, pagination, field properties (Key), and related tools despite no output schema. Provides sufficient guidance for an agent to use the tool effectively.

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

Parameters4/5

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

Schema coverage is 100%, but description adds value beyond schema by providing specific EntityId values, expand options, and cross-references to sibling tools. Baseline 3 is exceeded due to enriched context.

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?

The description clearly states the tool lists custom fields in Ploomes CRM. It distinguishes from sibling tools like ploomes_fields_types_list and ploomes_fields_entities_list by noting specific use cases and cross-references.

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?

Provides explicit filtering instructions with known EntityId values and directs to ploomes_fields_entities_list for complete mapping. Mentions $expand for related info and cross-references ploomes_fields_types_list for value properties. Lacks an explicit when-not-to-use but still offers clear 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

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/victorbenazzi/ploomes-mcp-server'

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