Skip to main content
import_disavow_rules Import a Google-format disavow file (up to 500 rules per call) as inert proposals. Existing rules are kept unchanged. approve:true is honoured only for a signed-in owner or administrator; agents always suggest. approved is true only when every imported rule ended up active; otherwise failed names the rules to review again.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
This operation changes saved state. Review its inputs and retry behavior before calling.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

Proposals are inert until a human owner or administrator approves them. Agent credentials cannot approve, reject or delete rules. Export records deterministic active-rule content and its hash; it never submits a file to Google.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • rules (array, required).
  • created (integer, required): Number of records created by this operation.
  • unchanged (integer, required).
  • revision (integer, required): Recorded revision. For an update, use the revision argument named by that operation.
  • approved (boolean, optional).
  • counts (object, optional).
  • warnings (array, optional).
  • failed (array, optional).
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

This write is annotated idempotent without a caller-supplied idempotency key. Reconcile saved state after an uncertain response, then use the same inputs for the same intended operation. Do not add an unsupported key. Operation-specific errors include INVALID_DISAVOW_INPUT, DISAVOW_CHECK_CAPACITY, HUMAN_ADMIN_REQUIRED, DISAVOW_NOT_READY, DISAVOW_REVISION_CONFLICT, DISAVOW_RULE_NOT_FOUND, DISAVOW_RULE_CONFLICT, DISAVOW_SCOPE_CLOSED, DISAVOW_CAPACITY, DISAVOW_EXPORT_CAPACITY, DISAVOW_IMPORT_TOO_LARGE, DISAVOW_RULE_TOO_LARGE, INVALID_CURSOR. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

This operation has no separate resource alias. Use its generic command route in a matching environment.

Continue

list_disavow_rules · list_disavow_exports Follow the related workflow. See capability status for availability or the command index for another operation.