Skip to main content
Glama

pipelines_movement_statistics

Get deal movement statistics for a pipeline over a specified time period, including new, won, lost deals, stage transitions, and average deal age to track pipeline velocity and identify bottlenecks.

Instructions

Get deal movement statistics in a pipeline for a specific time period.

Returns comprehensive statistics about how deals moved through the pipeline, including new deals, won/lost deals, and average deal age.

Response includes:

  • movements_between_stages: Count of stage transitions

  • new_deals: Count, IDs, values of new deals created

  • deals_left_open: Deals still in pipeline

  • won_deals: Successfully closed deals

  • lost_deals: Lost opportunities

  • average_age_in_days: Deal duration metrics by stage

Workflow tips:

  • Requires start_date and end_date in YYYY-MM-DD format

  • Defaults to authorized user unless user_id is specified

  • Values returned in multiple currencies

  • Use to understand pipeline velocity and deal flow

  • Track deal aging and identify stalled deals

Common use cases:

  • Monthly pipeline report: { "id": 1, "start_date": "2023-10-01", "end_date": "2023-10-31" }

  • Track team member activity: { "id": 1, "start_date": "2023-01-01", "end_date": "2023-12-31", "user_id": 123 }

  • Analyze deal flow patterns

  • Monitor sales cycle length

  • Identify pipeline bottlenecks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the pipeline
start_dateYesStart date in YYYY-MM-DD format (e.g., 2023-01-01)
end_dateYesEnd date in YYYY-MM-DD format (e.g., 2023-12-31)
user_idNoID of user to fetch statistics for (optional, defaults to authorized user)
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes the returned statistics in detail, implying a read operation, but does not explicitly state the tool is read-only, require permissions, or mention rate limits. The description adds value but lacks full transparency.

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 with clear sections (what it does, response includes, workflow tips, common use cases) and is informative without excessive fluff. Slightly lengthy but justified by richness of detail.

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 no output schema, the description thoroughly explains the response structure (movements_between_stages, new_deals, etc.). It covers all parameters and their usage. It is complete enough for an agent to invoke without ambiguity.

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 coverage is 100% with parameter descriptions. The description adds value by specifying date format requirements, optional user_id behavior, and providing example combinations for common use cases, exceeding the schema alone.

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 'Get deal movement statistics in a pipeline for a specific time period.' It includes a specific verb and resource, and distinguishes itself from siblings like 'pipelines_conversion_statistics' by focusing on movement data such as new/won/lost deals, stage transitions, and deal age.

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?

The description provides workflow tips (date format, user default) and common use cases with JSON examples, guiding when to use the tool. However, it does not explicitly state when not to use it or mention alternatives, though siblings are named.

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