Skip to content
v0.3

read.internal.cluster_admin

One customer cluster’s sheet: its rule, its members (paginated, with their score, phone and status, and who pinned them and when) and the promotions conditioning on it. Searching the members by name/e-mail requires the pii.read scope — without it the read refuses a search rather than answering an empty list. INTERNAL only.

  • Surface: GET /v1/read/internal/cluster_admin · MCP tool read.internal.cluster_admin
  • Auth:Internal read (operator) — a tenant credential is REQUIRED; requires the customer.admin.write scope. The tenant is resolved from the CALLER’s identity, never from store. Personal fields come back MASKED for an actor without pii.read (the shape is unchanged).
{
"properties": {
"cluster_id": {
"minLength": 1,
"type": "string"
},
"limit": {
"default": 24,
"maximum": 100,
"minimum": 1,
"type": "integer"
},
"page": {
"default": 1,
"maximum": 9007199254740991,
"minimum": 1,
"type": "integer"
},
"q": {
"minLength": 1,
"type": "string"
}
},
"required": [
"cluster_id"
],
"type": "object"
}

Open (unknown) — this capability does not declare an output schema.

validation_failed (400) · not_found (404) · unauthorized (401) · forbidden (403)