Skip to main content
Glama
Sign In

Scrapewise

by ai.scrapewise
OverviewDiscussionsAdmin

scrapewise_search_scraper_seo_fields

Read-onlyIdempotent
        Fetches SEO metadata (title, description, og:* tags) for the given URL. Same
        extraction logic as scrapewise_get_scraper_seo_fields but takes a URL in the
        body instead of looking up a scraper's pre-configured source. Subject to the
        SSRF deny-list — internal / link-local URLs return 400 SSRF_BLOCKED.

        Args:
          - body (SeoFieldsRequestDTO, required):
            - url (string): the URL to fetch SEO fields for. Must be a public HTTP(S)
              URL; internal-network URLs are rejected.

        Returns:
          `List<SeoField>` — same shape as scrapewise_get_scraper_seo_fields.

        Examples:
          - Use when: "what does the og:image look like on https://example.com?" → url
          - Don't use when: the URL is one of the customer's existing scrapers' sources
            → use scrapewise_get_scraper_seo_fields (cached, faster)

        Error Handling:
          - 400 SSRF_BLOCKED if the URL resolves to a blocked CIDR or hostname.
          - 502 if the URL is unreachable.
          - 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_search_scraper_seo_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful context beyond that: SSRF deny-list enforcement, 400 SSRF_BLOCKED, 502 unreachable, 401 Unauthorized, and 500 INTERNAL. It also clarifies that extraction logic matches the sibling and describes the return shape.

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 definition is front-loaded with purpose and sibling differentiation, then organized into Args, Returns, Examples, and Error Handling. The extra detail is justified by the SSRF and error behavior rather than being redundant.

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 read-only URL-fetching tool with no output schema, the description supplies the important missing context: allowed URL type, SSRF restrictions, return shape, and failure modes. It does not need to explain structured return values because none are provided, and the listed errors cover the main operational cases.

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?

Schema description coverage is 0%, so the description must carry the parameter semantics, and it does: body is required, nested url is required, and the URL must be a public HTTP(S) URL subject to internal-network rejection. This meaningfully compensates for 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: fetch SEO metadata (title, description, og:* tags) for a given URL. It also explicitly distinguishes this from scrapewise_get_scraper_seo_fields by explaining that this tool takes a URL in the body instead of using a scraper's pre-configured source.

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 an explicit 'Use when' example and a clear 'Don't use when' condition, naming scrapewise_get_scraper_seo_fields as the alternative and explaining that the sibling is cached and faster. This leaves little ambiguity about when to select this tool.

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