Refresh MCP Connector Tools

post

https://api.ycloud.com/v2/metaBusinessAgents/{entityId}/connectors/{connectorId}/refreshMCPTools

Triggers Meta to rediscover the MCP tools exposed by this connector. The request has no body. A successful HTTP 200 returns the current Connector; inspect mcp_tool_sync.status because remote discovery or provisioning failure can still return HTTP 200 with status ERROR. This operation has no idempotency key. Do not retry it automatically; after a timeout, query the Connector because the refresh outcome is uncertain.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Refresh request completed. Inspect mcp_tool_sync.status for discovery outcome.

400The request is invalid.

401A valid API key is required.

403The tenant does not own the requested resource or lacks the required Meta permission.

404The requested Meta Business Agent resource was not found.

409The requested operation conflicts with the current resource state.

429Too many requests were sent to YCloud or Meta.

500An internal server error occurred.

502Meta Business Agent returned an invalid or unavailable upstream response.