Get an API recipe
get_api_recipeThe exact HTTP request a CDP's own developer docs give for an everyday job: send an event (send_event), create or update a profile (upsert_profile), send a batch of events (send_batch), look up a profile (read_profile) or delete a person (delete_user). Each request is written with one shared example (customer u_1001, ada@example.com, order ord_5001) and checked with the rules of CdpHub's agent readiness test; none was sent to the vendor's API. Where the CDP doesn't offer the job, or its docs couldn't be read, the answer says why. Covers the 30 CDPs in the agent readiness test and names the others. Placeholders in angle brackets are for the caller to fill in.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"cdp": "<cdp>"
},
"name": "get_api_recipe"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cdp | Yes | The CDP, by name or by its CdpHub slug, for example "Braze", "Segment" or "treasure-ai". | |
| job | No | The job. Leave it out to get all five. |