Skip to main content
Glama
victorbenazzi

Ploomes MCP Server

Update Deal

ploomes_deals_update
Idempotent

Update existing deals in Ploomes CRM by providing only the fields to change. Move deals across stages or pipelines, and update custom fields using OtherProperties.

Instructions

Update an existing deal in Ploomes CRM. Only provided fields are changed. Use StageId to move a deal between stages within the same pipeline or to a different pipeline — use ploomes_pipelines_list then ploomes_stages_list to find valid stage IDs. ContactId and PersonId both reference /Contacts but serve different roles: ContactId = company/organization, PersonId = individual person. DealNumber is read-only and auto-generated — do not set it. Use OtherProperties to update custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDeal ID to update
TitleNoDeal title
ContactIdNoCompany/organization contact ID (from /Contacts).
PersonIdNoIndividual person contact ID (from /Contacts). Often an employee of the company in ContactId.
StageIdNoPipeline stage ID. Set this to move the deal to a different stage or pipeline. Use ploomes_pipelines_list then ploomes_stages_list to find valid IDs.
OwnerIdNoOwner user ID. Use ploomes_users_list to find valid user IDs.
AmountNoDeal monetary value
CurrencyIdNoCurrency ID. Use ploomes_currencies_list to find valid IDs.
OriginIdNoOrigin ID. Use ploomes_contacts_origins_list to find valid IDs.
OtherPropertiesNoCustom field values to update. Each entry must include FieldKey and exactly one value field (StringValue, IntegerValue, DateTimeValue, BoolValue, BigStringValue, or ObjectValueName). Use ploomes_fields_list to discover available field keys for deals.
Behavior4/5

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

Annotations indicate idempotent and not destructive. Description adds that only provided fields are changed (partial update) and that DealNumber is read-only. No contradiction.

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

Conciseness5/5

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

Description is concise with clear sentences, front-loaded with main purpose, and includes important warnings and clarifications without unnecessary verbosity.

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 required usage, stage transitions, custom fields, and read-only field warnings. References sibling tools for discovery. Could mention return behavior but acceptable without output schema.

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 coverage is 100%, but description adds significant value: explains ContactId vs PersonId roles, warns not to set DealNumber, and details OtherProperties for custom fields, including value type guidance.

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 deal in Ploomes CRM' and specifies 'Only provided fields are changed', distinguishing it from create, delete, list, and other sibling tools.

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 guidance on using StageId for stage transitions, references sibling tools for valid IDs, clarifies ContactId vs PersonId roles, and warns about DealNumber. Lacks explicit when-not-to-use, but context from siblings implies alternatives.

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