Skip to main content
Glama

deals_get_deals_timeline

Group deals by day, week, month, or quarter to forecast revenue and analyze trends over time using a date field like expected close date.

Instructions

Get deals timeline grouped by intervals.

Returns open and won deals grouped by a defined interval of time set in a date-type field.

Workflow tips:

  • Useful for revenue forecasting and trend analysis

  • Group deals by day, week, month, or quarter

  • Use field_key to specify which date field to use (e.g., add_time, update_time, close_time, expected_close_date)

  • Filter by user, pipeline, or custom filter

  • Set exclude_deals to true to get only summary data

  • Use totals_convert_currency for multi-currency reporting

Common use cases:

  • Monthly revenue forecast: { "start_date": "2024-01-01", "interval": "month", "amount": 12, "field_key": "expected_close_date" }

  • Weekly deal creation trends: { "start_date": "2024-01-01", "interval": "week", "amount": 8, "field_key": "add_time" }

  • Quarterly sales pipeline: { "start_date": "2024-01-01", "interval": "quarter", "amount": 4, "field_key": "close_time", "pipeline_id": 1 }

  • User performance: { "start_date": "2024-01-01", "interval": "month", "amount": 6, "field_key": "won_time", "user_id": 123 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateYesThe date when the first interval starts (YYYY-MM-DD)
intervalYesThe type of interval
amountYesThe number of intervals to fetch
field_keyYesThe date field key to retrieve deals from
user_idNoFilter by user ID
pipeline_idNoFilter by pipeline ID
filter_idNoFilter by filter ID
exclude_dealsNoWhether to exclude deals list (1) or not (0)
totals_convert_currencyNo3-letter currency code for converted totals
Behavior4/5

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

With no annotations provided, the description adequately conveys that this is a read-only operation returning grouped deal data. It mentions 'Returns open and won deals,' implying no side effects, though it could explicitly state read-only nature.

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 a summary, workflow tips, and examples. It is concise yet informative, front-loading the purpose. Clear organization aids agent scanning.

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 9 parameters (4 required) and no output schema, the description provides sufficient context through examples and tips. It could elaborate on result format or limitations, but the use cases cover common needs adequately.

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 all 9 parameters (100% coverage). The description adds value by listing common field_key values (add_time, etc.) and providing concrete use cases with example parameter combinations, enhancing understanding beyond the schema.

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: 'Get deals timeline grouped by intervals' and explains it returns open and won deals. This distinguishes it from sibling tools like deals_list or deals_get by specifying the temporal grouping aspect.

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?

Workflow tips and common use cases with example JSON objects provide clear context for when to use the tool. While it doesn't explicitly state when not to use it, the examples (e.g., monthly forecast, weekly trends) effectively illustrate appropriate scenarios.

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