Skip to main content
Glama
CorgiCorner

Bisibility

by CorgiCorner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Load more backlink rows

load_more_backlink_rows

Fetch additional backlink rows by extending the current unexpired snapshot in 100-row increments with its snapshot_ref.

Instructions

Requires API write scope. Extends the current unexpired backlinks snapshot at the per-100-row provider rate. Requires the exact snapshot_ref from the latest successful analysis or append response; use the replacement reference returned by each append. Returns 409 snapshot_expired when no current snapshot exists. Stale, mismatched or expired references return 409 before provider work; read or analyze the current snapshot before retrying. This tool cannot extend failed current-response summary evidence.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of additional rows to fetch, in multiples of 100 up to 1000.
targetYesDomain or full page URL matching the current unexpired snapshot.
project_idYesProject id whose provider budget and snapshot are used.
snapshot_refYesExact opaque snapshot_ref from the latest successful analysis or append response. Pass it unchanged; each append returns a replacement reference.
target_scopeNoSite or page scope matching the current unexpired snapshot.
include_subdomainsNoInclude backlinks to subdomains for site targets. Ignored for page targets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.1
    • addedInput schema / properties / snapshot_ref
      Added value: +{
+  "description": "Exact opaque snapshot_ref from the latest successful analysis or append response. Pass it unchanged; each append returns a replacement reference.",
+  "maxLength": 32768,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "target"
-]New value: +[
+  "project_id",
+  "snapshot_ref",
+  "target"
+]
  2. First observedv0.6.1

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare non-read-only, open-world, non-destructive. The description adds substantial behavioral context beyond that: required API write scope, per-100-row provider billing, 409 behavior for stale/mismatched/expired references before provider work, and the fact that each append returns a replacement reference. These are exactly the auth, rate/credit, and failure-mode details the annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the hard prerequisite ('Requires API write scope') and proceeds through snapshot_ref semantics, error behavior, and recovery in five dense sentences with no filler. Every sentence contributes operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a stateful append tool with no output schema, the description covers prerequisites, provider cost, error states, reference replacement, and a limitation on retrying failed evidence. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description restates the snapshot_ref lifecycle ('exact snapshot_ref from the latest successful analysis or append response; use the replacement reference') which the schema already documents, and adds little new syntax or format meaning for the six parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource+scope: 'Extends the current unexpired backlinks snapshot at the per-100-row provider rate.' It clearly distinguishes this append operation from sibling analysis tools like analyze_backlinks by focusing on extending an existing snapshot and consuming provider rows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit prerequisites ('Requires the exact snapshot_ref from the latest successful analysis or append response; use the replacement reference returned by each append'), an exclusion ('cannot extend failed current-response summary evidence'), and recovery guidance ('read or analyze the current snapshot before retrying'). The 409 snapshot_expired condition tells the agent exactly when not to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools