Skip to main content
Glama

deals_mark_as_lost

Mark a deal as lost and optionally record the reason to track pipeline loss patterns and improve sales processes.

Instructions

Mark a deal as lost.

Updates the deal status to "lost" and optionally records the reason why the deal was lost.

Workflow tips:

  • Automatically moves deal to lost stage

  • Lost reason helps track why deals fail

  • Triggers lost deal notifications and automations

  • Use for pipeline health and loss analysis

  • More convenient than using deals/update with status field

  • Lost reason is important for improving sales process

Common use cases:

  • Mark deal as lost: { "id": 123 }

  • Mark with reason: { "id": 123, "lost_reason": "Competitor pricing" }

  • Common lost reasons: "No budget", "Chose competitor", "Timing not right", "No response"

  • Track loss patterns for improvement

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal to mark as lost
lost_reasonNoReason why the deal was lost
Behavior4/5

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

With no annotations, the description discloses key behavioral traits: status change, lost reason recording, automatic stage move, notifications, and automations. Missing permission details but covers major side effects.

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?

Organized into workflows and use cases; mostly concise with minor redundancy (e.g., repeating 'mark a deal as lost'). Efficient but could be slightly tighter.

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?

For a simple two-parameter tool with no output schema, the description fully covers all necessary context: effect, usage patterns, common reasons, and pipeline impact.

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 100% of parameters. Description adds value beyond schema by providing concrete examples, common lost reasons, and emphasizing the importance of lost_reason for analysis.

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's purpose: marking a deal as lost by updating its status to 'lost'. It differentiates from siblings like deals_update and deals_mark_as_won by highlighting convenience and specific outcome.

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 workflow tips and common use cases, including explaining when to use this tool over deals_update. Offers common lost reasons but lacks explicit 'when not to use' 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/iamsamuelfraga/mcp-pipedrive'

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