createReview
Add a review record directly to import legacy reviews, create test data, or automate review submissions from external integrations.
Instructions
Create a review - Create a new review record. Writes live data.
Use when: importing legacy reviews from another platform, adding placeholder reviews for test data, or scripting review submissions from an external integration. Real member-submitted reviews come through the BD review form - only use this API when bypassing that form.
Required: user_id, review_email.
Parameter interactions:
user_id- the member being reviewedrating_overall: integer 1-5 (higher = better)recommend:0=No,1=Yes (shown as a thumbs-up recommendation flag)review_statuscontrols initial visibility - default flow is0Pending -> admin review
See also: updateReview (modify existing).
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": {
"user_id": "<user_id>",
"review_email": "<review_email>"
},
"name": "createReview"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | ||
| recommend | No | ||
| review_name | No | Reviewer's display name. Strongly recommended - most BD themes render this on the profile next to the review. | |
| review_email | Yes | REQUIRED (server rejects with `The review email is required` when omitted, despite earlier docs that listed only `user_id` as required). Reviewer's email. Used for notification threading and duplicate-review detection. | |
| review_title | No | ||
| review_status | No | Review status (integer). Authoritative values from BD admin: 0 = Pending (newly submitted, awaiting moderation - default for new reviews) 2 = Accepted (approved and visible on the member profile) 3 = Declined (rejected by admin - not publicly visible) 4 = Waiting for Admin (member pre-accepted, admin sign-off required) Value 1 is NOT a documented status - **but BD does NOT reject it. Passing `1` stores `"1"` verbatim with undefined render behavior.** Stick to the documented set. On create, default flow starts at 0. | |
| rating_overall | No | ||
| rating_results | No | Omitted on create -> BD stores 5 (server default), not null - send every category score you have. | |
| rating_service | No | Omitted on create -> BD stores 5 (server default), not null - send every category score you have. | |
| rating_language | No | Omitted on create -> BD stores 5 (server default), not null - send every category score you have. | |
| rating_response | No | Omitted on create -> BD stores 5 (server default), not null - send every category score you have. | |
| rating_expertise | No | Omitted on create -> BD stores 5 (server default), not null - send every category score you have. | |
| review_description | No |