Call a data endpoint
call_endpointRun one endpoint and return its JSON response. Spends the call's credits from the user's balance on success only; failed calls are free. Pass parameters exactly as get_endpoint lists them (array parameters as JSON arrays). The result reports credits used and remaining. Errors come back with a code: invalid_parameters (fix the parameters and retry), not_found (no data for these parameters), rate_limited or temporarily_unavailable (wait and retry), insufficient_credits, restricted_endpoint (the user must accept the restricted-endpoint terms in their dashboard), invalid_api_key (the MCP server config needs a valid API key). Responses over 100,000 characters are truncated; use paging or limit parameters to fetch less.
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": {
"endpoint": "<endpoint>"
},
"name": "call_endpoint"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | No | Parameters for the endpoint, e.g. {"listing_id": "18648717"}. | |
| endpoint | Yes | Endpoint ID from search_endpoints, e.g. "airbnb.listing". |