Get a project
get_projectUse this when you need one project's details in a single call: its public page URL, pipeline stages, capture forms (with the identity each one collects) and headline audience numbers. Use it after list_projects and before a write. Not for arrival rates over time (use get_audience_stats) or for finding a project's handle (use list_projects).
Each form lists its fields (key, label, type, required) and requires_verification, which is the form's "Ask people to verify their email" switch. Use them to tell the founder what a person sees on the signup form and what they receive afterward: when it is on, a new signup is sent an email asking them to verify their address, and when it is off they are not.
The forms list tells you which frm_… handle to pass to capture_signup and what identity that form expects: a form that collects a phone number will not accept an email. The stages list gives the exact stage keys update_contact_stage accepts; the founder renames these, so never guess one.
Counts here are precomputed aggregates, not a scan, so this is cheap even on a million-contact audience.
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": {
"project": "<project>"
},
"name": "get_project"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project | Yes | The project handle, like `prj_…`. From `list_projects`. |