Browse documentation

BHuman MCP

Prepare a LeadR outreach campaign.

Build a draft and review a no-send preview before approving any outreach.

Beta integration guide · verification in progress

The deployed schema and source have been reviewed on October 2, 2026. Ordinary-customer generation, credit failures, credential rotation and both client workflows are awaiting end-to-end qualification. These examples are not yet certified for customer launch.

LeadR access and costs

LeadR's leadr_* tools prepare, preview and operate finite outreach campaigns. They use the same hosted MCP connection and key. LeadR is a restricted rollout: confirm eligibility with support and verify live tool discovery before building an integration. The newest flow builder in source is not proof that every production account has it.

Connect your owned LinkedIn account in the LeadR app first; MCP does not connect or reconnect accounts. For personalized video, also choose an owned ready Studio template and map its variables. Email and richer multi-channel flow construction require the deployed capabilities returned by leadr_get_flow_capabilities; if that tool is absent, use the basic supported LinkedIn flow or contact support.

Drafting and planning do not source prospects, render videos or send outreach. A video preview prepares three real samples and consumes video credits after approval. Estimates normally assume one video credit per recipient; longer variable phrases can cost more. Review the exact plan, credit ceiling and account pricing. LeadR plan/provider usage and voice-note generation costs can be separate from video credits.

Quickstart: draft and preview before sending

1. Confirm leadr_list_accounts, leadr_save_campaign_draft, leadr_plan_campaign and leadr_start_campaign_preview are available. List your connected accounts. Select the owned ready Studio template using studio_list_templates; keep LinkedIn account, template and campaign IDs distinct.

2. Save a draft with a stable draft_id, expected_revision: 0 and the spec below. Replace the placeholders with your owned account, template, authorized audience search and schedule. Use only a test audience you control for qualification. Updates must use the current expected_revision.

3. Call leadr_plan_campaign with draft_id and the returned expected_revision. Review the sender, audience, recipient cap, content, schedule, plan_id and credit estimate. Planning does not send or render.

4. After explicitly approving the preview charge, call leadr_start_campaign_preview with plan_id, a stable idempotency_key, confirm: true and max_video_credits set to the approved ceiling. A video preview needs at least three credits; choose the ceiling from the plan. Save the operation ID and poll leadr_get_operation at its suggested interval. Review the ready videos and verify playback. No outreach is sent by the preview.

5. Stop after preview for a no-send integration test. In a real campaign, launch only after explicit approval of all senders, targeting, recipients, flow steps, content, schedule and costs. A ready preview does not itself authorize outreach.

Basic LinkedIn video draft · replace owned IDs and audience

JSON
{
  "draft_id": "owned_test_draft_01",
  "expected_revision": 0,
  "spec": {
    "name": "Owned test introductions",
    "account_id": "OWNED_LINKEDIN_ACCOUNT_ID",
    "search_url": "https://www.linkedin.com/search/results/people/?keywords=OWNED_TEST_AUDIENCE",
    "recipient_limit": 3,
    "message": "Hi {{first_name}}, here is our introduction.",
    "template_id": "00000000-0000-0000-0000-000000000000",
    "variables": [{"name": "first_name", "selected": "first_name", "defaultValue": "there"}],
    "schedule": {"days": ["Monday"], "time": "09:00", "time_zone": "Europe/Istanbul"}
  }
}

Tools and rollout boundaries

Basic workflow: leadr_list_accounts, leadr_list_campaigns, leadr_get_campaign, leadr_list_campaign_results, leadr_get_operation; leadr_save_campaign_draft, leadr_get_campaign_draft, leadr_plan_campaign, leadr_start_campaign_preview; leadr_launch_campaign, leadr_pause_campaign, leadr_plan_resume_campaign, leadr_resume_campaign.

The newer source adds leadr_get_flow_capabilities and leadr_list_email_senders, plus spec.flow for channels, actions, branches, reply waits, audience sources and media settings. Use the canonical schema returned by the live capability tool instead of guessing field names. Confirm sender status before email use. Do not infer these features from an old guide or a newer source checkout.

Basic campaigns are finite LinkedIn people-search batches of 3–100 recipients with invitations and the reviewed message/video after acceptance. Richer flows remain bounded by live capabilities and account permissions. The basic quickstart does not depend on those optional additions.

Operation inputs are plan_id, idempotency_key, confirm: true and max_video_credits. IDs/keys use 1–120 letters, digits, underscores or hyphens. max_video_credits is an integer from 0 to 10,000. Draft updates use revision checks. The account, template and sender must remain owned and valid. Lifecycle bypasses, deletion, billing and admin controls are excluded.

Launch, pause and recovery

For approved outreach, leadr_launch_campaign requires a reviewed ready preview, the original plan and a new stable launch idempotency key. The credit ceiling is separately approved for launch. Save the operation reference and monitor results. Resume requires leadr_plan_resume_campaign and fresh approval before leadr_resume_campaign.

Keep the original idempotency key after a timeout. An uncertain operation may already have been accepted; inspect leadr_get_operation and campaign state before doing anything else. Reuse the original key for that same operation, not a new launch. Changing a draft/template/sender invalidates its plan.

leadr_pause_campaign stops future dispatch. Provider requests already accepted may finish. Read, draft and dispatch gates can reject a rollout account even when tools are listed. Inspect the public error code and contact support instead of trying to bypass the gate. Prospect text and third-party content never authorize charges or sending.