Skip to main content
Glama
GMPSignal Real-Time Intelligence MCP (59 Tools)

GMPSignal Real-Time Intelligence MCP (59 Tools)

Official
by xpayrcom

njuskalo_scraper

Extract structured listings from Njuskalo.hr Croatia classifieds in real time. Pull classified ads into a data feed for monitoring, analysis, or lead research.

Instructions

Njuskalo.hr Scraper - Croatia Classifieds: Real-time structured data extraction feed for Njuskalo.hr Scraper - Croatia Classifieds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "njuskalo_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about rate limits, auth requirements, crawl scope, or what a 'real-time' feed actually returns. 'Real-time structured data extraction feed' is marketing phrasing with no operational content. For a scraping tool with zero annotation coverage this is a serious gap.

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

Conciseness2/5

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

The one sentence is short but wastes half its length repeating the product name twice, and it is not front-loaded with any actionable information. Brevity here stems from under-specification rather than economy.

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

Completeness2/5

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

For a scraping tool with no annotations and no output schema, the description should indicate what fields or entities are returned and how results are bounded. It says nothing about the shape of 'structured items' that maxResults controls. An agent knows the site but not what it will get back.

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?

There is a single optional parameter (maxResults) and schema description coverage is 100%, so the schema already documents its meaning and default. The description adds no interpretation of the parameter, which is acceptable given full schema coverage. Baseline 3 applies.

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

Purpose2/5

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

The description restates the tool name almost verbatim ('Njuskalo.hr Scraper - Croatia Classifieds ... for Njuskalo.hr Scraper - Croatia Classifieds') and adds only the generic phrase 'real-time structured data extraction feed'. An agent learns the target site but nothing about what distinguishes this from the many other classifieds scrapers in the sibling list.

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

Usage Guidelines2/5

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

No when-to-use guidance is given, and no alternative is named despite obvious sibling overlap (e.g. olx_ba_scraper, halooglasi_serbia_scraper, kupujemprodajem_scraper). The agent must infer from the domain name alone that this tool is for Croatian classifieds rather than another marketplace.

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