Skip to main content
Glama

scrapewise_create_scraper_site

        A Site is the address list (link list) of ONE automation: the automation runs once
        over every address on it. This endpoint creates or updates a Site by id (empty
        body.id = create; set id = update). Subject to the SITE_MAP plan feature.

        IMPORTANT: leaving out `id` creates a NEW Site on every call, but a scraper's run (and
        scrapewise_get_scraper_site) reads only one Site per scraper — a list saved into a second
        Site may never be scraped. Before saving, read the scraper's Site
        (scrapewise_get_scraper_site) and send its `id`; omit `id` only when the scraper has no
        Site yet, and make that first save on its own, not in parallel with another save for the
        same scraper. For an API (cURL) scraper, send every link together with its `curl` in the
        same save, unless the Site has `calculateCurlsAutomatically` on.

        There are two ways to give an automation its addresses:
          1. PASTED / UPLOADED list — send `links` (one {url, title} per address). The list
             REPLACES the stored one. To add addresses, send the full new list.
          2. FED list — set `linksSourceScraperId` (another automation of this account),
             `urlFieldName` / `titleFieldName` (which of its result columns hold the address
             and the title) and `updateLinksBySourceScraperAutomatically: true`; the list is
             then refreshed from that automation's rows after every run of it. You do NOT
             fetch those rows yourself and you never call a `/urls` endpoint — the server
             copies them.
        Storing a list turns the automation's list mode on by itself: no follow-up
        scrapewise_create_scraper call is needed. To create an automation, attach a list
        and run it in ONE call, use scrapewise_run_scraper_url_list instead.
        Do NOT create one scraper per address — one automation holds the whole list.

        Args:
          - body (SiteDTO, required): the owning scraper (`scraperId`) and either `links`
            (pasted list) or `linksSourceScraperId` + `urlFieldName` (fed list).

        Returns:
          The persisted SiteDTO including assigned id, and `linksDropped` (fed lists only:
          how many offered addresses this automation cannot read and did not store).

        Examples:
          - Use when: "give automation {id} these 50 URLs" → scraperId + links
          - Use when: "feed automation B from automation A's results" → scraperId (B) +
            linksSourceScraperId (A) + urlFieldName
          - Don't use when: you want to create an automation for a list and run it → use
            scrapewise_run_scraper_url_list (one call)
          - Don't use when: you want to add links to an existing site → there is no
            add-links endpoint; re-PUT the full SiteDTO with the whole new list

        Error Handling:
          - 402 if customer plan lacks SITE_MAP feature.
          - 400 if body validation fails.
          - 400 if a PASTED link (no `linksSourceScraperId`) does not belong to this
            scraper. A scraper that reads one kind of page runs its whole URL list
            through that same reader, so every link must be a web address of that kind
            and must carry everything that kind of read needs (for example the dates a
            stay lookup needs, the postcode a store lookup needs, the type a trend
            lookup needs). The message names the offending link and what is wrong with
            it; nothing is guessed and nothing is silently dropped.
          - A FED list (`linksSourceScraperId` set) is not refused whole: the links this
            scraper can read are stored and the rest are DROPPED and COUNTED, on
            `X-Links-Dropped` and on `linksDropped` in the body. A source column
            legitimately carries addresses of other kinds, and one of them must not cost
            the dependent scraper its whole list. 400 only when NOTHING offered is
            readable — and then the previously stored list is kept untouched.
          - 401 Unauthorized.

[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_create_scraper_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesthe owning scraper (`scraperId`) and either `links` (pasted list) or `linksSourceScraperId` + `urlFieldName` (fed list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / description
      Added value: +"the owning scraper (`scraperId`) and either `links` (pasted list) or `linksSourceScraperId` + `urlFieldName` (fed list)."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-idempotent, non-destructive write. The description adds substantial behavior beyond that: 402 when the SITE_MAP plan feature is missing, per-link 400 rejection for pasted lists with nothing dropped, partial-storage-with-counting for fed lists via X-Links-Dropped/linksDropped, and the rule that a first save must not run in parallel with another save for the same scraper. It also warns that omitting id silently creates a duplicate Site that may never be scraped, which is exactly the kind of trap an agent needs disclosed.

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?

Well front-loaded (definition, then the create/update rule, then the hazard), and the numbered list modes plus Args/Returns/Examples/Error Handling structure make it scannable. It is long, and there is some repetition — the replace-not-append rule appears both in mode 1 and again in the 'Don't use when' example — which keeps it from a 5.

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 single-parameter but semantically dense mutation tool with no output schema, the description covers return values (persisted SiteDTO with assigned id and linksDropped), the full error matrix, and the dynamic-response caveat is handled by the runtime hint. An agent has everything needed to call it correctly on a first attempt.

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

Parameters5/5

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

With 100% schema coverage the baseline would be 3, but the description goes well past the schema by establishing the mutual exclusivity of the two list modes, the create-vs-update meaning of id, the replace-not-append semantics of links, and the required pairing of linksSourceScraperId with urlFieldName/titleFieldName plus updateLinksBySourceScraperAutomatically. It also clarifies that calculateCurlsAutomatically relaxes the obligation to supply curl per link.

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 first sentence defines the resource precisely (a Site is the address list of one automation), and the second states the verb plus its dual mode: create when body.id is empty, update when set. It is clearly distinguishable from scrapewise_get_scraper_site, scrapewise_run_scraper_url_list, and scrapewise_update_scraper_site_from_source, all named in the body.

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 when-to-use and when-not-to-use rules with named alternatives: read the existing Site and resend its id rather than creating a second one, use scrapewise_run_scraper_url_list to create-and-run in one call, and there is no add-links endpoint so the full list must be re-PUT. Two concrete 'Use when' examples and two 'Don't use when' exclusions leave nothing to inference.

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.