Skip to main content
propose_competitors Save up to 10 proposed competitors, each with its relationship, audience, topic and evidence pages. Rejected sites stay rejected. Does not add them to the set or start lookups.
Hosted availability unverified: this name is absent from the 2026-10-27 deployment evidence. Check your connected catalog before calling. 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

Saves up to ten proposals, each with its relationship, audience, topic and up to five evidence pages. A proposal never changes the approved set or starts a lookup; the person adds it through the competitor set. Each result names its outcome: proposed, updated, unchanged (the same reason again), already_a_competitor, your_website, previously_rejected, duplicate_in_request or suggestion_limit_reached. A rejected site stays rejected until decide_competitor_suggestion restores it. The 50-suggestion limit counts proposals not yet in the set. A candidate may include expectedRevision and expectedSnapshot from the same saved suggestion. Supply both together; null for both requires absence. A changed row, active set revision or proposal count returns 409 COMPETITOR_SUGGESTION_CHANGED and rolls back the whole batch. Read the current suggestions and set before trying again.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions. 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_COMPETITOR_SUGGESTION_INPUT, COMPETITOR_SUGGESTIONS_UNAVAILABLE, READ_ONLY_MEMBER, PROJECT_NOT_FOUND. 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

suggest_competitors Follow the related workflow. See capability status for availability or the command index for another operation.