Skip to main content
import_link_watches Import up to 100 known backlinks. Each row returns its position and success or error. accepted includes existing placements; created counts only new watches. Invalid rows do not prevent valid rows from being imported.
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.
Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.

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

Each watch row uses monitor_link defaults: targetScope exact and cadenceSeconds 86400 when omitted; omitted expectations and localReference are empty. Each row is processed separately. Invalid rows produce indexed errors while valid rows continue. accepted includes reused watches; created counts only new watches. Relation expectations allow at most twenty tokens, each one to forty letters, digits, _ or -; values are lowercased, deduplicated and sorted.

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 command is not annotated idempotent. After a timeout, inspect existing state before repeating a write. 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

list_link_watches Follow the related workflow, inspect capability status, or return to the command index.