Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Planned for future release
Workspace App Connect
Created by Guest
Created on Jun 30, 2026

RELATED IDEAS

A small editor for MCP tool descriptions in the Web UI, readable by both the agent and a human

When you expose a REST API as an MCP tool, you set a description per tool. It gets pre-filled from the OpenAPI spec, and you can edit it, but the editing experience is bare. [one line on the current field limitation, e.g. single cramped input, no structure, no line breaks].

The description is the part of an MCP tool that matters most. It's what the agent reads to decide whether to call the tool and how to call it, and it's also what a person reads when they're trying to understand what the server actually exposes. A thin or untouched auto-generated description gets the tool called wrong, or not called at all.

Give that field a small, proper editor. Nothing heavy. Enough room to write a few lines, basic structure like line breaks and a list, and ideally a short hint of what a good description looks like. The point is to make it easy to write and update something meaningful instead of fighting a one-line box.

It has to read well for two audiences at the same time: the agent invoking the tool, and the person maintaining the server.

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.