[power-automate][Bug] get_operation_details returns empty parameters: {} for many real, valid operations

[Augus611]

Plugin

power-automate

Plugin Version

2.2.0

Skill / Command

N/A (MCP tool: get_operation_details)

Bug Description

get_operation_details, meant to return exact parameter names/types/enums for a connector operation, returns an empty parameters object for several confirmed-valid, commonly-used operations — including ones with non-trivial parameter schemas. This makes it unreliable as a source of truth for constructing action JSON by hand; the only reliable way found to discover a real parameter shape during this work was inspecting an actual successful designer-driven save.

Steps to Reproduce

1. Call get_operation_details for connector: "shared_office365", operation: "SendEmailV2".
2. Call it for connector: "shared_excelonlinebusiness", operation: "RunScriptProdV2".
3. Call it for connector: "shared_onedriveforbusiness", operation: "GetFileContentByPath".
4. Observe all three return "parameters": {} despite each operation having real, non-trivial parameters (confirmed via other means, e.g. inspecting an actual saved flow's JSON).

Expected Behavior

Returns the actual parameter names, types, and (where applicable) enum values for the operation.

Actual Behavior

{
  "operationId": "SendEmailV2",
  "connector": "shared_office365",
  "summary": "Send an email (V2)",
  "actionType": "OpenApiConnection",
  "parameters": {}
}

(same empty-parameters pattern for the other two operations listed above)

Relevant Logs / Screenshots

Exact empty-parameters response shown above, reproduced for 3 distinct connectors/operations.

Environment

• OS: Windows (build 10.0.22631.7376)
• Claude Code version: 2.1.220
• PAC CLI: not installed / not used for this work

---

🤖 This issue was created using the /report-issue skill.

[radioblazer]

Thanks for raising! Fixed with the merge of #393, please raise if you continue to encounter after updating.

[Augus611]

Confirmed fixed in v3.0.1. Re-tested against all four operations from the original report (SendEmailV2, RunScriptProdV2, GetFileContentByPath, CopyFileAsync) — all now return real, populated parameter schemas matching actual production usage instead of empty {}.