Skip to main content
Glama

scrapewise_update_scraper_site_from_source

Idempotent
        Builds the link list (Site) of ONE automation from the latest run of ANOTHER automation
        of this account, on the server, and saves it. The call REPLACES the stored link list of
        that automation (the same save as scrapewise_create_scraper_site with a fed list, but
        you do not send the links: the server reads the source automation's latest results,
        takes the chosen column, drops empty and repeated addresses and stores the rest).
        Subject to the SITE_MAP plan feature.

        The list is the one today's portal "Scraper-based links" dialog would save: the same
        links, in the same order, with the same titles. A very big list can take minutes.
        The call can outlive a 60-second tool timeout; the save still completes. Before you
        retry, read the automation's site with scrapewise_get_scraper_site: when its
        `lastBuild.requestId` equals your `buildRequestId`, that build ended (`outcome` OK, or
        the refusal code and `message`). Retry with the SAME `buildRequestId` only for the same
        build; a finished OK build is then returned without building again.

        For a dedicated-endpoint automation the saved settings of that automation are added to
        each link by the server (the portal adds unsaved panel values too; this call cannot).

        Args:
          - body (SiteBuildFromSourceDTO, required): `scraperId` (the automation that gets the
            list), `linksSourceScraperId` (the automation whose latest results feed it),
            optional `urlFieldName` / `titleFieldName` (result columns; omit the title for
            empty titles), `updateLinksBySourceScraperAutomatically`,
            `calculateCurlsAutomatically`, and `buildRequestId` (a new UUID per build). There
            is no site id and no link list in the body.

        Returns:
          SiteBuildResultDTO: `site` (the saved SiteDTO with `linkCount`, `linksBuiltAt` and
          `lastBuild`), `feedCounts` (rows read, rows with no usable address, collapsed rows,
          repeated addresses, links built; null on a replay of a finished build) and
          `linksDropped` (built links this automation cannot read; not stored).

        Examples:
          - Use when: "feed automation B from the product links automation A found" →
            scraperId (B) + linksSourceScraperId (A) + urlFieldName
          - Use when: the source run is large — the list never passes through your context
          - Don't use when: you already hold the exact addresses → scrapewise_create_scraper_site
            with `links`
          - Don't use when: you want to create an automation for a list and run it → use
            scrapewise_run_scraper_url_list

        Error Handling:
          - 400 FEED_BUILD_EMPTY: the source has no finished run, or no usable address in that
            column; the existing list is kept.
          - 400 FEED_LIST_TOO_LARGE: the source run holds more links than one automation may
            feed another; the existing list is kept.
          - 400 LINK_FEED_NONE_ADMISSIBLE / LINK_SOURCE_NOT_FOUND / validation errors (ids must
            be automation ids, `buildRequestId` a UUID); nothing is changed.
          - 409 BUILD_REQUEST_REUSED: that `buildRequestId` was used for a different build.
          - 503 FEED_BUSY with Retry-After: another large link list is being prepared, or the
            list is being updated from its source right now; nothing was changed — call again
            after the Retry-After seconds.
          - 402 if the plan lacks the SITE_MAP feature. 401 Unauthorized. 500 INTERNAL.

[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "scrapewise_update_scraper_site_from_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes`scraperId` (the automation that gets the list), `linksSourceScraperId` (the automation whose latest results feed it), optional `urlFieldName` / `titleFieldName` (result columns; omit the title for empty titles), `updateLinksBySourceScraperAutomatically`, `calculateCurlsAutomatically`, and `buildRequestId` (a new UUID per build). There is no site id and no link list in the body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / description
      Added value: +"`scraperId` (the automation that gets the list), `linksSourceScraperId` (the automation whose latest results feed it), optional `urlFieldName` / `titleFieldName` (result columns; omit the title for empty titles), `updateLinksBySourceScraperAutomatically`, `calculateCurlsAutomatically`, and `buildRequestId` (a new UUID per build). There is no site id and no link list in the body."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), it discloses replacement semantics ('REPLACES the stored link list'), the SITE_MAP plan gate, that a big list can take minutes and outlive a 60s timeout while the save still completes, and how to verify completion via `lastBuild.requestId`. The error table (400 FEED_BUILD_EMPTY / FEED_LIST_TOO_LARGE, 409 BUILD_REQUEST_REUSED, 503 FEED_BUSY with Retry-After, 402) states what changes and what is preserved in each case.

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

Conciseness4/5

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

It is long, but front-loaded and sectioned (Args / Returns / Examples / Error Handling) so an agent can scan it. A few lines restate the same idea twice (the link-list replacement, the returned list equivalence), which costs some tightness without harming clarity.

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 nested-body mutation with no output schema, the description covers everything an agent needs: body roles, what the returned SiteBuildResultDTO contains (`site`, `feedCounts`, `linksDropped`), the timeout/polling path, replay semantics, and the full failure matrix. The one stated limitation (unsaved panel values cannot be added for dedicated-endpoint automations) is also disclosed.

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

Parameters4/5

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

Schema coverage is 100%, so the parameters are already documented; the description still adds meaning by naming the roles (dependent vs. source automation) and stressing that there is no site id and no link list in the body. The `buildRequestId` replay contract is restated as a new UUID per build, same id only for retrying that build, reinforcing rather than duplicating the schema.

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 opens with a precise verb+resource+scope: it builds the link list (Site) of one automation from the latest run of another automation and saves it. It explicitly contrasts the call with scrapewise_create_scraper_site (same save, but the server reads the links instead of you sending them), so an agent can separate it from the sibling without opening either schema.

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 'Use when' cases (feed automation B from product-links automation A; source run is large so the list never passes through context) and two 'Don't use when' cases routing to scrapewise_create_scraper_site with `links` and to scrapewise_run_scraper_url_list. Retry guidance is also scoped to the same build via `buildRequestId`.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.