Skip to main content
Glama

deals_update

Update specific fields of an existing deal. Provide only the fields to change, such as value, title, status, or stage.

Instructions

Update an existing deal.

Updates one or more fields of an existing deal. Only provide fields you want to change.

Custom fields:

  • Pass display names: { "id": 123, "custom_fields": { "Industria": "Tech", "Budget": 5000 } }

  • Or hash keys directly: { "id": 123, "custom_fields": { "abc123...": "raw value" } }

  • For enum/set fields, pass option labels (not ids).

Workflow tips:

  • Only specify fields you want to update

  • Use deals/get first to see current values

  • Use deals/move_to_stage for simple stage changes

  • To mark as won/lost, update status field

Common use cases:

  • Update value: { "id": 123, "value": 7500 }

  • Change title: { "id": 123, "title": "Updated Deal Name" }

  • Mark as won: { "id": 123, "status": "won" }

  • Update multiple fields: { "id": 123, "value": 10000, "expected_close_date": "2024-12-31", "probability": 75 }

  • Move to new stage: { "id": 123, "stage_id": 5 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal to update
titleNoDeal title
valueNoDeal value
org_idNoID of the organization
statusNoDeal status
user_idNoID of the user who will own this deal
currencyNo3-letter currency code
stage_idNoID of the stage
person_idNoID of the person
visible_toNoVisibility setting
lost_reasonNoReason why the deal was lost
pipeline_idNoID of the pipeline
probabilityNoDeal success probability (0-100)
custom_fieldsNoCustom field values keyed by display name or hash. See description for format.
expected_close_dateNoExpected close date in YYYY-MM-DD format
Behavior3/5

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

No annotations provided, so description must carry the burden. It explains partial update behavior and custom field formats, but does not mention permissions, error handling, or side effects. It covers the main behavior but lacks full transparency on constraints.

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?

Well-structured with a summary, custom fields section, workflow tips, and common use cases. Front-loaded with purpose. Slightly long but each section is relevant and earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 15 parameters and no output schema, the description is thorough: covers update behavior, custom fields complexity, workflow tips, and common use cases. It references sibling tools for specific actions, making it complete for typical usage.

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%, so baseline is 3. However, the description adds significant value: explains custom fields keys (display names vs hash), enum/set fields handling, and provides examples for common parameters like status, value, and stage_id, going beyond the schema descriptions.

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' and 'Updates one or more fields', using a specific verb and resource. It distinguishes from sibling tools like deals_create, deals_move_to_stage, and deals_mark_as_won by suggesting alternatives for stage changes and status updates.

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?

Explicitly says when to use ('only provide fields you want to change') and when not to (use deals/move_to_stage for simple stage changes, update status field for won/lost). Workflow tips and common use cases provide concrete guidance.

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/nubiia-dev/mcp-pipedrive'

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