Resolve the account and an existing ready page template; read existing pages before creating. Use the user's approved notes verbatim in the brief, then create/update the draft and require read-back. Failed verification is not permission to create a duplicate. Generation may publish and consume credits; request explicit approval before generating/publishing. Inspect saved page and engagement separately.
HivePages account engagement
pages.analytics.get.v2
Use when: Use the existing Core workflow: HivePages account engagement. Page engagement only; no program spend or cross-channel attribution.
Avoid when: Do not infer unsupported history, attribution, or commitments from this response.
Effects: Read only.
Cost: No gateway credit charge; reads saved workspace data without starting paid provider work. Gateway rate code: none; downstream billing may apply.
Access: accounts:read. Approval: operation authorization. Reads do not need an operation UUID.
Keep the same operation and operation_id when retrying identical work. Reconcile an uncertain result before new work; never replay an old V1 write under a new V2 ID.
Check status, execution_state, error_code, output and evidence/resource references. Queued work is not complete: poll jobs.status.get.v2 in domain.workspace.v2. For read-back verification require read_back_verified=true where returned; reconcile failures without creating another object.
Invocation example using fictional fixtures
{
"tool": "domain.pages.v2",
"arguments": {
"params": {
"action": "invoke",
"operation": "pages.analytics.get.v2",
"arguments": {},
"operation_id": "00000000-0000-4000-8000-000000000003"
}
},
"notice": "Fictional fixture IDs and example text. Resolve real IDs, use returned preview tokens and approve exact side effects before execution. Input validation is not proof of provider readiness or a successful business outcome."
}
Input schema: fields, defaults and constraints
{
"additionalProperties": false,
"properties": {
"engagement": {
"default": "all",
"description": "Engagement used by the pages analytics get input v2 operation.",
"enum": [
"all",
"engaged",
"clickers"
],
"title": "Engagement",
"type": "string"
}
},
"title": "McpPagesAnalyticsGetInputV2",
"type": "object"
}
Use when: Use the existing Core workflow: Create account HivePage draft. Creates a page using an existing/default template. Does not generate or publish page content; no account-plan task system.
Avoid when: Do not infer unsupported history, attribution, or commitments from this response.
Effects: Creates a page using an existing/default template. Does not generate or publish page content; no account-plan task system.
Cost: No gateway rate is configured. Check the Core workflow preview/quote for downstream charges and final settlement. Gateway rate code: none; downstream billing may apply.
Access: actions:execute. Approval: exact_scope_single_action. A stable operation UUID is required.
Keep the same operation and operation_id when retrying identical work. Reconcile an uncertain result before new work; never replay an old V1 write under a new V2 ID.
Check status, execution_state, error_code, output and evidence/resource references. Queued work is not complete: poll jobs.status.get.v2 in domain.workspace.v2. For read-back verification require read_back_verified=true where returned; reconcile failures without creating another object.
Invocation example using fictional fixtures
{
"tool": "domain.pages.v2",
"arguments": {
"params": {
"action": "invoke",
"operation": "pages.draft.create.v2",
"arguments": {
"account_id": "00000000-0000-4000-8000-000000000001"
},
"operation_id": "00000000-0000-4000-8000-000000000003"
}
},
"notice": "Fictional fixture IDs and example text. Resolve real IDs, use returned preview tokens and approve exact side effects before execution. Input validation is not proof of provider readiness or a successful business outcome."
}
Use when: Use the existing Core workflow: Update source-grounded HivePage brief. Updates the existing page brief. Does not generate content or publish; never invent customer conversations.
Avoid when: Do not infer unsupported history, attribution, or commitments from this response.
Effects: Updates the existing page brief. Does not generate content or publish; never invent customer conversations.
Cost: No gateway rate is configured. Check the Core workflow preview/quote for downstream charges and final settlement. Gateway rate code: none; downstream billing may apply.
Access: actions:execute. Approval: exact_scope_single_action. A stable operation UUID is required.
Keep the same operation and operation_id when retrying identical work. Reconcile an uncertain result before new work; never replay an old V1 write under a new V2 ID.
Check status, execution_state, error_code, output and evidence/resource references. Queued work is not complete: poll jobs.status.get.v2 in domain.workspace.v2. For read-back verification require read_back_verified=true where returned; reconcile failures without creating another object.
Invocation example using fictional fixtures
{
"tool": "domain.pages.v2",
"arguments": {
"params": {
"action": "invoke",
"operation": "pages.draft.update.v2",
"arguments": {
"brief": {},
"landing_page_id": "00000000-0000-4000-8000-000000000001"
},
"operation_id": "00000000-0000-4000-8000-000000000003"
}
},
"notice": "Fictional fixture IDs and example text. Resolve real IDs, use returned preview tokens and approve exact side effects before execution. Input validation is not proof of provider readiness or a successful business outcome."
}
Use when: Use the existing Core workflow: Generate and publish HivePage. Paid Core job generates, renders and PUBLISHES to S3. Requires explicit publication approval. Does not bypass readiness or overwrite manual edits. Poll jobs.status.get.v2 for job progress and pages.get.v2 for the resulting page.
Avoid when: Do not infer unsupported history, attribution, or commitments from this response.
Effects: Paid Core job generates, renders and PUBLISHES to S3. Requires explicit publication approval. Does not bypass readiness or overwrite manual edits. Poll jobs.status.get.v2 for job progress and pages.get.v2 for the resulting page.
Cost: No gateway rate is configured. Check the Core workflow preview/quote for downstream charges and final settlement. Gateway rate code: none; downstream billing may apply.
Access: actions:execute. Approval: exact_scope_single_action. A stable operation UUID is required.
Keep the same operation and operation_id when retrying identical work. Reconcile an uncertain result before new work; never replay an old V1 write under a new V2 ID.
Check status, execution_state, error_code, output and evidence/resource references. Queued work is not complete: poll jobs.status.get.v2 in domain.workspace.v2. For read-back verification require read_back_verified=true where returned; reconcile failures without creating another object.
Invocation example using fictional fixtures
{
"tool": "domain.pages.v2",
"arguments": {
"params": {
"action": "invoke",
"operation": "pages.generate.v2",
"arguments": {
"landing_page_id": "00000000-0000-4000-8000-000000000001"
},
"operation_id": "00000000-0000-4000-8000-000000000003"
}
},
"notice": "Fictional fixture IDs and example text. Resolve real IDs, use returned preview tokens and approve exact side effects before execution. Input validation is not proof of provider readiness or a successful business outcome."
}
Use when: Use the existing Core workflow: HivePage content and generation status. Existing account page, including generation status. Poll this after page generation.
Avoid when: Do not infer unsupported history, attribution, or commitments from this response.
Effects: Read only.
Cost: No gateway credit charge; reads saved workspace data without starting paid provider work. Gateway rate code: none; downstream billing may apply.
Access: accounts:read. Approval: operation authorization. Reads do not need an operation UUID.
Keep the same operation and operation_id when retrying identical work. Reconcile an uncertain result before new work; never replay an old V1 write under a new V2 ID.
Check status, execution_state, error_code, output and evidence/resource references. Queued work is not complete: poll jobs.status.get.v2 in domain.workspace.v2. For read-back verification require read_back_verified=true where returned; reconcile failures without creating another object.
Invocation example using fictional fixtures
{
"tool": "domain.pages.v2",
"arguments": {
"params": {
"action": "invoke",
"operation": "pages.get.v2",
"arguments": {
"landing_page_id": "00000000-0000-4000-8000-000000000001"
},
"operation_id": "00000000-0000-4000-8000-000000000003"
}
},
"notice": "Fictional fixture IDs and example text. Resolve real IDs, use returned preview tokens and approve exact side effects before execution. Input validation is not proof of provider readiness or a successful business outcome."
}
Use when: Use the existing Core workflow: Existing account HivePages. Existing account pages, not a durable account-plan or task system.
Avoid when: Do not infer unsupported history, attribution, or commitments from this response.
Effects: Read only.
Cost: No gateway credit charge; reads saved workspace data without starting paid provider work. Gateway rate code: none; downstream billing may apply.
Access: accounts:read. Approval: operation authorization. Reads do not need an operation UUID.
Keep the same operation and operation_id when retrying identical work. Reconcile an uncertain result before new work; never replay an old V1 write under a new V2 ID.
Check status, execution_state, error_code, output and evidence/resource references. Queued work is not complete: poll jobs.status.get.v2 in domain.workspace.v2. For read-back verification require read_back_verified=true where returned; reconcile failures without creating another object.
Invocation example using fictional fixtures
{
"tool": "domain.pages.v2",
"arguments": {
"params": {
"action": "invoke",
"operation": "pages.list.v2",
"arguments": {},
"operation_id": "00000000-0000-4000-8000-000000000003"
}
},
"notice": "Fictional fixture IDs and example text. Resolve real IDs, use returned preview tokens and approve exact side effects before execution. Input validation is not proof of provider readiness or a successful business outcome."
}
Input schema: fields, defaults and constraints
{
"additionalProperties": false,
"properties": {
"account_id": {
"anyOf": [
{
"format": "uuid",
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Exact account UUID returned by a Hivekind search, list, get, preview, or resource call.",
"title": "Account Id"
},
"search": {
"anyOf": [
{
"maxLength": 255,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Search used by the public pages list input v2 operation.",
"title": "Search"
}
},
"title": "McpPublicPagesListInputV2",
"type": "object"
}
Use when: Use the existing Core workflow: Existing HivePage templates. Read existing templates before draft creation. Selecting an existing template avoids automatic first-use template design.
Avoid when: Do not infer unsupported history, attribution, or commitments from this response.
Effects: Read only.
Cost: No gateway credit charge; reads saved workspace data without starting paid provider work. Gateway rate code: none; downstream billing may apply.
Access: accounts:read. Approval: operation authorization. Reads do not need an operation UUID.
Keep the same operation and operation_id when retrying identical work. Reconcile an uncertain result before new work; never replay an old V1 write under a new V2 ID.
Check status, execution_state, error_code, output and evidence/resource references. Queued work is not complete: poll jobs.status.get.v2 in domain.workspace.v2. For read-back verification require read_back_verified=true where returned; reconcile failures without creating another object.
Invocation example using fictional fixtures
{
"tool": "domain.pages.v2",
"arguments": {
"params": {
"action": "invoke",
"operation": "pages.templates.list.v2",
"arguments": {},
"operation_id": "00000000-0000-4000-8000-000000000003"
}
},
"notice": "Fictional fixture IDs and example text. Resolve real IDs, use returned preview tokens and approve exact side effects before execution. Input validation is not proof of provider readiness or a successful business outcome."
}