Tool reference · Account metadata
list_pipelines EngageBay MCP tool
Get every deal pipeline and its stages, in order — the lookup that makes stage-based deal filters actually work, since stage names repeat across pipelines but ids don't.
- Category
- Account metadata
- Permission needed
crm.deals.read- Access type
- Read-only
- Works with
search_crm_objectscount_crm_objects
On this page
What this tool does
Most EngageBay accounts have more than one deal pipeline — for example, a Sales pipeline and a Renewals pipeline — and it's common for different pipelines to reuse the same stage name, like “Negotiation.” Because of that, a filter on stage alone is ambiguous: EngageBay can't tell which pipeline's “Negotiation” you mean.
list_pipelines returns every pipeline on the account and its stages in order, with both a name (what you see in the app) and an id (what a deal record actually stores) for each. That id is what lets a stage filter be unambiguous.
Always pair a stage filter with a track_id condition. A filter on stage needs a track_id condition in the same group naming the pipeline — otherwise it may match a same-named stage in a different pipeline than you intend. See the filter syntax on the search_crm_objects page for the exact pattern.
What you can ask
“What pipelines do we have set up?”
“What are the stages in the Sales pipeline, in order?”
“Which deals in the Sales pipeline are still at Negotiation?” — list_pipelines resolves the pipeline and stage id, then search_crm_objects filters on them.
Related tools
search_crm_objectsandcount_crm_objects— use a pipeline's id astrack_idalongside any stage condition.
More tools
Use list_pipelines from your AI tool
Connect your AI tool to the EngageBay MCP server and ask in plain language — it calls the right tool for you.
