How to surface mcp server updates for an existing plugin

we recently had a plugin approved

after being published to the public, we made a small change to one tool description, however this change is not being reflected on chatgpt (web or desktop)

we tried reconnecting the plugin, deleting/installing without success

it seems to be caching the tool/list call at the version/submission level

do we need to make a new submission for this scenario?

what happens if we add/remove tools, do we need to make a new submission ?

are there any published docs that cover this matter ?

Thanks for flagging this, @jbrodriguez. What you’re seeing is expected: published tool metadata is stored as a reviewed snapshot, so reconnecting or reinstalling won’t refresh a changed tool description.

For changes to tool descriptions, names, schemas, or the tool list, create a new draft version of the existing app, scan the endpoint again, submit it for review, and publish it after approval. You do not need to create a brand-new app.

Adding tools should follow that same version flow. Removing or renaming tools can break the currently published version, so the recommended approach is to keep the existing contract available, add the replacement, then publish the approved update. The “Ongoing Maintenance” section of the submission docs covers these cases.

-Mark G.