Skip to main content
Glama

Power Automate MCP Server by Flow Studio

by io.github.ninihen1
OverviewDiscussionsAdmin

Resolve action inputs

resolve_live_parameters
Read-only

Resolve a connector action's inputs the way the flow designer does: dropdown options, list and table columns, folder and file pickers — every input in one call, or one with parameterName. Reads only: it runs the lookups the designer runs, never an action. Pass values you have in parameters; pass a display name in match to get back the value to write into the flow. An input whose parent is not known yet has status "needs". Inputs inside an object are addressed by key (body/recipient/groupId). Omit connectionName and one is chosen.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMax options per dropdown (default 200). A longer list is marked truncated.
matchNoExact display name, or the value itself, per input, e.g. { "folderPath": "Inbox" }. Case-insensitive, never fuzzy. Folders also take /path. matchCount 0 answers status "nomatch".
browseNoOpen a folder: { "field": "<input>", "id": "<folder value>" }.
detailNoColumn detail. Default compact.
searchNoNarrow long option or column lists by name (a filter, not a pick).
apiNameNoAlias for connectorName.
includeNoAdd "outputs" to get the fields this action returns.
flowNameNoWith actionName: take the connector, operation and connection from this flow action.
actionNameNoAction (or trigger) name in flowName.
parametersNoValues already chosen, e.g. { "dataset": "<site url>" }.
operationIdNoOperation ID, e.g. PostItem. Not needed with flowName + actionName.
connectorNameNoConnector name, e.g. shared_sharepointonline.
parameterNameNoResolve only this input. Omit for every input.
connectionNameNoConnection to run as. Omit to have one chosen.
environmentNameYesName of the Power Platform environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / dynamicMetadata
      Removed value: -{
-  "description": "Not needed for the operation's own inputs. For a list the connector does not describe, send its dropdown metadata; it runs through the designer's dropdown service.",
-  "type": "object"
-}
  2. Changed1 schema field changed
    • changedInput schema / properties / dynamicMetadata / description
      Previous value: -"Not needed for the operation's own inputs. For a list the connector does not describe (e.g. Dataverse ListRecords over connectionreferences), send its dropdown metadata; it runs through the designer's dropdown service."New value: +"Not needed for the operation's own inputs. For a list the connector does not describe, send its dropdown metadata; it runs through the designer's dropdown service."
  3. Changed1 schema field changed
    • changedInput schema / properties / dynamicMetadata / description
      Previous value: -"Not needed for the operation's own inputs. For a lookup the connector does not define (e.g. Dataverse ListRecords over connectionreferences) send it and it is used as given."New value: +"Not needed for the operation's own inputs. For a list the connector does not describe (e.g. Dataverse ListRecords over connectionreferences), send its dropdown metadata; it runs through the designer's dropdown service."
  4. Added

TDQS

Score is being calculated.

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