Every invocation needs mcp:tools:call plus one matching business scope. tools/list returns only tools allowed by the key's current scopes.
| Tool | Required business scope |
|---|---|
lucra.organization.get_context | brand:organization:read or partner:organization:read |
lucra.organization.update | brand:organization:write or partner:organization:write |
lucra.creators.search | brand:creator:read or partner:creator:read |
lucra.creators.discover | brand:creator:read or partner:creator:read |
lucra.programs.list | brand:programs:read or partner:programs:read |
lucra.programs.review_creator | brand:programs:review or partner:programs:review |
lucra.submissions.list | brand:submissions:read or partner:submissions:read |
lucra.submissions.review | brand:submissions:review or partner:submissions:review |
lucra.products.list | brand:products:read or partner:products:read |
lucra.ads.list | brand:ads:read or partner:ads:read |
lucra.analytics.summary | brand:analytics:read or partner:analytics:read |
lucra.finance.summary | brand:finance:read or partner:finance:read |
lucra.scopes.list and lucra.mcp.tools.list are utility tools available with mcp:tools:read.
Read tools accept client, cursor, from, limit, query, and to where relevant. Mutation input schemas are returned by both discovery endpoints.
Example call
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "lucra.submissions.review",
"arguments": {
"client": "acme",
"submissionId": "submission-slug",
"status": "Revision",
"note": "Trim the introduction to three seconds."
}
}
}
Successful tool results include both text content and structuredContent. Business failures use an MCP tool result with isError: true; JSON-RPC framing and validation failures use JSON-RPC error objects.
