Skip to main content
Glama

stages_update

Update an existing stage's name, order, probability, or rot rules. Provide only the fields to change.

Instructions

Update an existing stage.

Provide only the fields you want to change. To reorder stages within a pipeline, update the order_nr field.

Common use cases:

  • Rename: { "id": 5, "name": "Closed Won" }

  • Reorder: { "id": 5, "order_nr": 0 }

  • Adjust rot rules: { "id": 5, "is_deal_rot_enabled": true, "days_to_rot": 14 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStage ID to update
nameNoNew display name
order_nrNoNew position in the pipeline
days_to_rotNo
pipeline_idNoMove stage to a different pipeline
deal_probabilityNoDefault deal win probability 0-100
is_deal_rot_enabledNo
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses partial update behavior and reordering, but lacks details on side effects, permissions, or rate limits.

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?

Short, front-loaded with purpose, and uses examples efficiently. No unnecessary words.

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 main use cases for a 7-parameter update tool. Missing output schema details but not critical for typical usage.

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 covers 71% of parameters. Description adds value with examples showing how to use order_nr for reordering and rot rules configuration.

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 clearly states the verb 'Update' and resource 'stage', with specific examples. It distinguishes from sibling tools like stages_create or stages_delete.

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 to provide only changed fields and includes common use cases. Lacks explicit when-not-to-use but context is clear enough.

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