Skip to main content
Glama
Sign In

Scrapewise

by ai.scrapewise
OverviewDiscussionsAdmin

scrapewise_get_scraper_seo_fields

Read-onlyIdempotent
        Returns SEO metadata (title, description, og:* tags, etc.) extracted from the
        scraper's configured source URL. Cached at the SEO field service layer; multiple
        calls within the cache TTL are cheap. Use for descriptive context about what site
        the scraper targets without scraping any product data.

        Args:
          - id (string, path param, required): the scraper's MongoDB ObjectId.

        Returns:
          `List<SeoField>` — one SeoField per discovered meta tag (name, content).
          Empty list if the source URL has no extractable meta tags.

        Examples:
          - Use when: "what site does scraper {id} target? give me its title and OG image"
          - Don't use when: you want SEO fields for an arbitrary URL not tied to a
            scraper → use scrapewise_search_scraper_seo_fields with a URL body

        Error Handling:
          - 400 (CustomerError envelope) if no scraper with the given id exists for this customer.
          - 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": {
      "id": "<id>"
    },
    "name": "scrapewise_get_scraper_seo_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this is read-only, idempotent, non-destructive, and closed-world. The description adds meaningful context beyond that: SEO fields are cached at the service layer with cheap repeat calls within the TTL, an empty list is returned when no meta tags exist, and specific 400/401/500 error conditions are enumerated. It stops short of specifying the actual TTL value or pagination behavior, keeping it at a strong 4.

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?

The text is front-loaded with purpose and caching behavior, then structured into Args, Returns, Examples, and Error Handling sections. Every section adds information, though the Examples are slightly verbose relative to the single-parameter surface.

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?

With one parameter, no output schema, and rich annotations, the description covers what the tool returns (List<SeoField>, one per meta tag, empty list if none), the cached behavior, error cases, and how it differs from the sibling search tool. An agent has everything needed to call it correctly.

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 0% and the schema only says the single id is a string. The description compensates by identifying it as the scraper's MongoDB ObjectId, noting it is a required path parameter, and tying it to the scraper resource. That is useful meaning beyond the bare 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 states a specific verb and resource: returns SEO metadata (title, description, og:* tags) extracted from the scraper's configured source URL. It explicitly distinguishes this from scraping product data and from the sibling search tool that handles arbitrary URLs.

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 provides an explicit 'Use when' example (asking what site a scraper targets) and a 'Don't use when' rule that names the correct alternative, scrapewise_search_scraper_seo_fields, along with the distinguishing condition (arbitrary URL not tied to a scraper).

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

All Scrapewise toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources