Skip to main content
Glama
victorbenazzi

Ploomes MCP Server

Update Contact

ploomes_contacts_update
Idempotent

Update specific fields of a Ploomes contact by ID. Only the fields you provide are changed; omitted fields stay the same.

Instructions

Update an existing contact in Ploomes CRM by ID. Only provided fields are changed; omitted fields remain untouched.

To find valid IDs for reference fields:

  • TypeId: use ploomes_contacts_types_list (typically 1=Person, 2=Company, but may vary per account)

  • StatusId: use ploomes_contacts_status_list to discover available contact statuses

  • OriginId: use ploomes_contacts_origins_list to discover available contact origins

  • OwnerId: use ploomes_users_list to discover valid user IDs

  • CityId: numeric city ID from the Ploomes cities database

  • CurrencyId: numeric currency ID from the Ploomes currencies list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID to update. The unique numeric identifier of the contact in Ploomes.
NameNoContact name. Full name for a person or company name.
TypeIdNoContact type ID. Use ploomes_contacts_types_list to discover valid values. Typically 1=Person, 2=Company, but values may vary per account.
LegalNameNoLegal / registered company name. Useful for companies that have a trade name different from the legal name.
RegisterNoTax identification number (CPF for individuals or CNPJ for companies in Brazil).
IdentityDocumentNoIdentity document number (e.g., RG in Brazil).
EmailNoPrimary email address for the contact.
PhoneNoPrimary phone number as a string. For multiple phones, use the Phones array instead.
PhonesNoArray of phone numbers with type. Each entry has PhoneNumber (required), TypeId (optional), and CountryId (optional).
StatusIdNoContact status ID. Use ploomes_contacts_status_list to discover valid values for your account.
CompanyIdNoParent company contact ID. Links this person to a company contact already in Ploomes.
OwnerIdNoOwner user ID. The user responsible for this contact. Use ploomes_users_list to discover valid user IDs.
OriginIdNoOrigin ID. How this contact was acquired. Use ploomes_contacts_origins_list to discover valid values.
StreetAddressNoStreet address (street name). E.g.: "Rua Augusta"
StreetAddressNumberNoStreet address number. E.g.: "1234"
StreetAddressLine2NoAddress complement / additional info. E.g.: "Sala 56", "Apto 12"
NeighborhoodNoNeighborhood / district name.
ZipCodeNoZip / postal code (numeric only, formatting is stripped automatically). E.g.: "01310100" or "01310-100"
CityIdNoCity ID from the Ploomes cities database. Numeric identifier for the city.
NoteNoFree-text note or general observations about the contact.
WebsiteNoWebsite URL. E.g.: "https://www.example.com"
RevenueNoAnnual revenue as a numeric value.
SkypeNoSkype username or ID.
FacebookNoFacebook profile URL or username.
LatitudeNoGeographic latitude coordinate. E.g.: -23.5505
LongitudeNoGeographic longitude coordinate. E.g.: -46.6333
CurrencyIdNoCurrency ID for monetary values associated with this contact.
EmailMarketingNoWhether the contact has opted in to receive email marketing. true = opted in, false = opted out.
OtherPropertiesNoCustom field values. Use ploomes_fields_list to discover available fields. Each entry needs a FieldKey and exactly one value field (StringValue, IntegerValue, DateTimeValue, BoolValue, BigStringValue, or ObjectValueName).
Behavior4/5

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

The description adds value beyond annotations by disclosing that the update is partial ('Only provided fields are changed; omitted fields remain untouched'). Annotations already mark it as idempotent and non-destructive, and the description reinforces this with concrete behavioral detail.

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?

The description is well-structured: first sentence states purpose, second explains partial update, then lists reference field helpers. At 7 sentences, it is not overly long, though the list of lookup tools could be slightly more compact. Front-loading is good.

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 high parameter count (29) and no output schema, the description covers essential aspects: partial update, how to find reference values, and custom field structure. It omits response details but that is acceptable without output schema. Sufficient for a complex tool.

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?

With 100% schema description coverage, the baseline is 3. The description adds extra context for reference parameters (TypeId, StatusId, etc.) by listing discovery tools, and for custom fields under OtherProperties it explains the value fields. This exceeds mere schema repetition.

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 'Update an existing contact in Ploomes CRM by ID' and distinguishes itself from create/delete siblings by specifying partial update behavior ('Only provided fields are changed'). The verb+resource+scope is specific and unambiguous.

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?

While the description does not explicitly state when to use vs alternatives, it provides extensive guidance for populating reference fields by listing specific sibling tools (e.g., ploomes_contacts_types_list, ploomes_users_list). This helps the agent know how to find valid values, but lacks direct exclusion criteria.

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