mcp_get_flows

Summary

Field	Value
Tool name	get_flows
MCP title	List Power Automate cloud flows and run history
Category	standard
Implementation	DynamicsCrm.DevKit.Cli/Mcp/Tools/GetFlowsTool.cs
Estimated token count	~359 tokens (tools/list tool JSON, o200k_base, measured 2026-06-18)
Last verified	2026-06-18

MCP Tool Description (Exact)

Power Automate cloud flows + run history. Modes: no flow_id = list (filtered); flow_id + action='list' = detail + last 5 runs; flow_id + action='runs' = extended run history. For classic (category=0) workflows use get_workflows.

WHEN TO USE:
- List flows by name/owner/status
- Inspect a specific flow + recent runs
- Drill into run history with status_filter (debug failures)

Fuzzy on name_filter / owner_filter: 0/multi → tool returns disambiguation list and stops; AI must ask user. 1 → auto.

Parameters

Name	Type	Required	Default	Description
flow_id	string	No	""	GUID. Empty = list. Set: action determines detail vs runs.
action	string	No	"list"	'list' or 'runs'. 'runs' needs flow_id.
name_filter	string	No	""	list only. Name contains.
owner_filter	string	No	""	list only. Owner contains.
status	string	No	"active"	'active' / 'draft' / 'suspended' / 'all'.
status_filter	string	No	""	runs only: succeeded/failed/running/cancelled/waiting/paused/skipped/suspended.
minutes_ago	integer	No	1440	runs only. Max 43200.
max_records	integer	No	50	1–250.

Input Schema

{
  "type": "object",
  "properties": {
    "flow_id": {
      "type": "string",
      "description": "GUID. Empty = list. Set: action determines detail vs runs.",
      "default": ""
    },
    "action": {
      "type": "string",
      "description": "'list' or 'runs'. 'runs' needs flow_id.",
      "default": "list"
    },
    "name_filter": {
      "type": "string",
      "description": "list only. Name contains.",
      "default": ""
    },
    "owner_filter": {
      "type": "string",
      "description": "list only. Owner contains.",
      "default": ""
    },
    "status": {
      "type": "string",
      "description": "'active' / 'draft' / 'suspended' / 'all'.",
      "default": "active"
    },
    "status_filter": {
      "type": "string",
      "description": "runs only: succeeded/failed/running/cancelled/waiting/paused/skipped/suspended.",
      "default": ""
    },
    "minutes_ago": {
      "type": "integer",
      "description": "runs only. Max 43200.",
      "default": 1440
    },
    "max_records": {
      "type": "integer",
      "description": "1–250.",
      "default": 50
    }
  },
  "required": []
}

Related MCP Resources

Resource	URI / URI template	MIME type	Reason
server_logic_guide	docs://server_logic_guide	text/markdown	Inferred from source: Filtering patterns, list/detail modes, and entity scoping for server-logic tools. Read this when get_plugins, get_workflows, get_flows, etc. returns an error.

When To Use

• List flows by name/owner/status
• Inspect a specific flow + recent runs
• Drill into run history with status_filter (debug failures)

Notes

• Use the exact MCP description and parameter schema above as the authoritative contract.

Example

{
  "flow_id": "string"
}

Output

Returns CallToolResult from the MCP server. The response content and structured fields follow the tool implementation and model returned by GetFlowsTool.get_flows.

Prompt Examples

• "List active cloud flows owned by this user and show their recent run status."
• "Open this flow and summarize the last five runs, especially failures."
• "Show failed runs for this flow in the last 24 hours and include error details."