Power Platform Community Forum Thread Details

Description:

We are building a Copilot Studio agent that integrates with a remote MCP server exposing multiple tools (7+), each requiring an accountId as an input parameter.

Issue Summary:

Even though accountId is captured and stored in a Copilot variable (conversation context), Copilot Studio does not automatically map or reuse this variable when invoking subsequent MCP tools that expect accountId as an input.

As a result, the agent repeatedly prompts the user for accountId, even though it is already available in the context.

Example Scenario:

User is asked for accountId at the start of the conversation.
- User inputs: abcd1234-5678-90ef-gh12-ijkl345678mn
- Value is stored in a Copilot variable: accountId
2. First tool invoked: get-booking-request-list
- Requires: accountId
- ❌ Issue: Despite the value being stored in context, Copilot prompts the user again instead of auto-filling from the accountId variable

Expected Behavior:

Once a required value like accountId is stored in the conversation context, Copilot Studio should automatically bind and pass it to any tool that declares it as an input parameter.
Users should not be prompted again for known context values unless they are missing, outdated, or explicitly overridden.

Request for Guidance:

We are seeking clarity on:

How to configure Copilot Studio so that tools automatically use context variables like accountId as input parameters.

Whether this behavior is currently supported in Copilot Studio or MCP tool bindings.

If not supported, is there a roadmap or plan to enable automatic parameter binding from conversation context to avoid unnecessary re-prompts?

This capability is essential to build a seamless, natural, and intelligent multi-step agent experience where shared data like accountId can persist across tools without user repetition.

Categories:

Model context protocol