Skip to main content
Glama
Sign In

Power Automate MCP Server by Flow Studio

by io.github.ninihen1
OverviewDiscussionsAdmin

Describe connector

describe_live_connector
Read-only

Describe a live Power Platform connector/API and its operations. Use mode=summary (default) to get a compact operation catalog. Use operationId to describe one operation, including inputs, outputs, dynamic parameter metadata, nextTool hints to call resolve_live_parameters, and an authored hint + canonical example shape (when one exists) to copy into update_live_flow. Use search without connectorName/apiName to search operations across connectors and get connection-aware suggestions. Use mode=full only when raw OpenAPI connector metadata is required.

Input Schema

NameRequiredDescriptionDefault
topNoMax operations to return in connector summary mode, or max top search results to show in cross-connector search. Default 250 for summary, 10 for search display.
typeNoOperation usage to include in summary mode. Default Action.
depthNosummary (default): compact operation catalog. full: raw OpenAPI metadata.
searchNoOptional operation search text. With connectorName, filters that connector summary. Without connectorName, searches operations across connectors.
apiNameNoAlias for connectorName.
variantNoWhen an operation has multiple authored variants (e.g. shared_teams/PostMessageToConversation has channel/groupchat/flowbot_chat), pass a specific variantKey to get that variant's hint and exampleDefinition. Omit to receive a hint listing the available variants.
operationIdNoOptional operation ID to describe with expanded inputs and outputs.
connectorNameNoConnector logical name, for example shared_teams. Either connectorName/apiName is required, unless search is provided for cross-connector operation search.
environmentNameYesName of the Power Platform environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / apiName / description
      Previous value: -"Alias for connectorName, matching Canvas MCP describe_api naming."New value: +"Alias for connectorName."
  2. Changed2 schema fields changed
    • addedInput schema / properties / depth
      Added value: +{
+  "description": "summary (default): compact operation catalog. full: raw OpenAPI metadata.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / mode
      Removed value: -{
-  "description": "summary (default): compact operation catalog. full: raw OpenAPI metadata.",
-  "enum": [
-    "summary",
-    "full"
-  ],
-  "type": "string"
-}
  3. Changed3 schema fields changed
    • changedInput schema / properties / connectorName / description
      Previous value: -"Connector logical name, for example shared_teams. Either connectorName or apiName is required."New value: +"Connector logical name, for example shared_teams. Either connectorName/apiName is required, unless search is provided for cross-connector operation search."
    • changedInput schema / properties / search / description
      Previous value: -"Optional operation search text applied to name, summary, description, tags, and visibility."New value: +"Optional operation search text. With connectorName, filters that connector summary. Without connectorName, searches operations across connectors."
    • changedInput schema / properties / top / description
      Previous value: -"Max operations to return in summary mode. Default 250."New value: +"Max operations to return in connector summary mode, or max top search results to show in cross-connector search. Default 250 for summary, 10 for search display."
  4. Changed1 schema field changed
    • addedInput schema / properties / variant
      Added value: +{
+  "description": "When an operation has multiple authored variants (e.g. shared_teams/PostMessageToConversation has channel/groupchat/flowbot_chat), pass a specific variantKey to get that variant's hint and exampleDefinition. Omit to receive a hint listing the available variants.",
+  "type": "string"
+}
  5. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered; the description usefully adds what each mode returns (compact catalog, expanded inputs/outputs, dynamic parameter metadata, nextTool hints). It does not mention auth or permission requirements, and it references a non-existent 'mode' parameter when the schema calls it 'depth', which slightly muddies invocation.

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?

Front-loaded with the core purpose and then organized by mode, with no filler. It is dense and slightly repetitive ('Use ... Use ... Use') and the depth/mode term drift is a small structural wart, but nothing is padding.

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?

For a 9-parameter, no-output-schema tool this covers the decision space well: mode selection, cross-connector search, per-operation expansion, and nextTool handoffs. The main gap is the unexplained divergence between the description's 'mode' and the schema's 'depth' parameter, which an agent must resolve on its own.

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 coverage is 100%, so the baseline is 3, but the description adds real cross-parameter semantics beyond the schema: search without connectorName switches to cross-connector search, operationId enables expanded output, and variant selects among authored hints/examples. The only loss is the depth-vs-mode naming mismatch.

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?

States a specific verb and resource (describe a live Power Platform connector/API and its operations) and scopes it against the flow-oriented siblings like get_live_flow and update_live_flow. An agent can pick this out as the connector-metadata tool without opening the schema.

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?

Gives explicit routing for each mode: summary as default, operationId for a single operation, search without connectorName for cross-connector lookup, and full only when raw OpenAPI metadata is required. It also names adjacent tools (resolve_live_parameters, update_live_flow) so the agent knows the natural next step.

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