Search actions with Embedded MCP

Use search-actions to find an app action, inspect a suggested match, and page through published actions.

search-actions lists the actions in an app's latest published version. Pass an appRef from search-apps.

Input	Use
`appRef`	Required app slug or ID.
`q`	Optional task or exact action slug.
`limit`	Actions per page, 1 to 50. Default 20.
`cursor`	`data.nextCursor` from the previous page.

{"appRef":"slack","q":"send a message","limit":20}

{"success":true,"data":{"items":[{"id":"action_slack_send","slug":"sendMessage","name":"Send Message","operation":"create"}],"limit":20,"nextCursor":null}}

When q has one clear match, the response can include suggestedAction.action with its schema. Use it to prepare the call. For other matches, call get-action-schema. Follow nextCursor when it is present.

The server does not list hidden actions. If you know an action name but cannot find it, check the app's published version.