Skip to main content
request_competitor_inventory Request an inventory lookup for one approved member and revision from the configured owned corpus. Candidates remain unchecked. No supplier spending or monitoring enrollment. Missing corpus rows never prove backlink absence. Requires owned-corpus admission and a loaded corpus; unavailable configurations need an operator change, not a retry.
Hosted MCP registration verified. These schemas describe the development contract; confirm supported inputs with tools/list. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL_API_URL; production does not expose these command routes.
Provider-backed admission requires enabled configuration and available allowance; registration alone does not make retrieval available. Inspect usage and the run’s coverage before interpreting results.

Example request

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

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. 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

backlinksStatus, excludeInternalBacklinks, pageLimit and rowLimit are required explicit policies, with no omitted-input defaults. The member supplies the previously approved target scope. This operation needs configured owned-corpus admission. It does not accept an arbitrary provider field, buy supplier data or enroll monitoring.

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

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_discovery_run · capture_competitor_inventory Follow the related workflow, inspect capability status, or return to the command index.