# Resolve an Embedded MCP lookup

Resolve an action argument such as a channel name to the ID required by a MindCloud app action.

`resolve-lookup` finds the ID for an action argument marked `needsResolution` in its schema. It uses the end user's connection and requires Run Workflows access.

```json
{
  "appRef": "slack",
  "actionRef": "sendMessage",
  "argumentKey": "channel",
  "q": "team-updates"
}
```

```json
{
  "success": true,
  "data": {
    "status": "resolved",
    "nextCursor": null,
    "selected": {
      "value": "C123",
      "label": "team-updates"
    }
  }
}
```

Pass `selected.value` as the action argument. `status: "ambiguous"` returns `candidates`; ask the user to choose one. `status: "not_found"` has no selected value. Matching is exact-first and ignores case.

An ambiguous result looks like this:

```json
{
  "success": true,
  "data": {
    "status": "ambiguous",
    "nextCursor": null,
    "candidates": [
      {
        "value": "C123",
        "label": "team-updates"
      },
      {
        "value": "C456",
        "label": "team-updates-archive"
      }
    ]
  }
}
```

Required inputs are `appRef`, `actionRef`, and `argumentKey`. Optional inputs are `q`, `limit` (1 to 50, default 10), `cursor`, and `connectionRef`. Use `connectionRef` when the user has several accounts for the app. Follow `nextCursor` to inspect more candidates.