Skip to main content
Glama

Power Automate MCP Server by Flow Studio

by io.github.ninihen1
OverviewDiscussionsAdmin

list_live_flows

Read-only

List Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (default): flows you own plus flows shared with you (personal + team), with full definitions. mode=admin: all flows in the environment (requires an admin account). mode=admin with includeDeleted=true also returns soft-deleted flows (state=Deleted) — the only way to find a deleted flow. If search is provided, results are filtered to flows whose displayName contains the search text. For large environments pagination is time-bounded — if nextLink is returned, pass it as continuationUrl to retrieve the next batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMax flows to return. Paginates automatically. Omit for all.
modeNoowner (default): user-scoped — owned + shared-with-me flows (personal + team), with full definitions. admin: admin-scoped endpoint, all flows.
searchNoOptional case-insensitive filter applied to flow displayName.
includeDeletedNoInclude soft-deleted flows, which come back with state=Deleted and can be restored with restore_live_flow. Requires mode=admin — the user-scoped listing never returns deleted flows. Off by default.
timeoutSecondsNoStop collecting pages after this many seconds and return a nextLink for the next batch. Default 25. Max 55.
continuationUrlNonextLink value returned by a previous call. Pass to resume pagination from where the last call stopped. Must match the same mode as the original call.
environmentNameYesName of the Power Platform environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeDeleted
      Added value: +{
+  "description": "Include soft-deleted flows, which come back with state=Deleted and can be restored with restore_live_flow. Requires mode=admin — the user-scoped listing never returns deleted flows. Off by default.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"owner (default): user-scoped endpoint, owned flows only with full definitions. admin: admin-scoped endpoint, all flows."New value: +"owner (default): user-scoped — owned + shared-with-me flows (personal + team), with full definitions. admin: admin-scoped endpoint, all flows."
  3. Changed1 schema field changed
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Optional case-insensitive filter applied to flow displayName.",
+  "type": "string"
+}
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context beyond that: the distinction between owner and admin modes (including permission requirements), the behavior of includeDeleted (returning soft-deleted flows), time-bounded pagination with nextLink, and the requirement for continuationUrl to match the original mode. No contradictions with annotations.

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 dense but well-organized, starting with the core purpose and moving through modes, filtering, and pagination. Every sentence adds value, and the structure is logical. It is slightly long but justified given the number of parameters and behaviors it must explain; still, it could be trimmed slightly without loss.

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?

With 7 parameters and no output schema, the description carries the full burden of explaining what the tool returns and how pagination works. It lists the return fields (id, displayName, state, triggerType, lastModifiedTime), explains mode-dependent scoping, and covers the continuationUrl mechanism. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description enriches several parameters: it clarifies that includeDeleted requires mode=admin and is off by default, that continuationUrl must match the original mode, that top paginates automatically, and that timeoutSeconds limits collection. These details are not in the schema descriptions and are essential for correct invocation.

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 verb (list), resource (Power Automate flows), and scope (in an environment). It enumerates the returned fields and distinguishes modes (owner vs admin) and the inclusion of deleted flows. This sets it apart from siblings like get_live_flow (single flow) and list_store_flows (store flows), so an agent can immediately identify the correct tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit guidance on when to use each mode: owner for user-scoped flows, admin for all flows with admin privileges, and admin+includeDeleted for finding deleted flows, explicitly stating this is 'the only way to find a deleted flow.' It also explains the search filter and pagination continuation, leaving no ambiguity about when to call this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Power Automate MCP Server by Flow Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources