Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wccftech_article

Fetch a Wccftech article by its canonical URL and return structured JSON with title, authors, section, images, body paragraphs, and paywall status.

Instructions

Get a Wccftech article. Returns one Wccftech article by its canonical url on wccftech.com or www.wccftech.com, covering news, reviews, how-tos, roundups and best-of pages. The response has the title, description, authors, section, times, lead image and body paragraphs where the site serves them, plus a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Wccftech article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.3/5.0
Behavior4/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. It discloses the return fields (title, description, authors, section, times, lead image, body paragraphs) and the conditional nature of body content, plus a paywalled flag, though it does not describe failure modes or fetch behavior.

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?

Three front-loaded sentences with no filler: the first states the action, the second narrows scope and accepted hosts, and the third enumerates the return payload because no output schema exists.

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-URL article tool with no output schema or annotations, the description supplies the domain constraints, content coverage, and response shape an agent needs. No important gap remains.

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% and the single url parameter already documents 'Canonical Wccftech article URL'. The description adds the allowed host variants (wccftech.com and www.wccftech.com), which is a modest but useful clarification beyond 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?

Specific verb+resource ('Get a Wccftech article') and precise scope ('one Wccftech article by its canonical url on wccftech.com or www.wccftech.com'), making it distinguishable from list-oriented siblings like wccftech_headlines and wccftech_news even without naming them.

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

Usage Guidelines3/5

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

The description explains it returns one article by its canonical URL, which implies usage when a specific article URL is known, but it never names alternatives such as wccftech_headlines, wccftech_news, or wccftech_sections, nor does it state when not to use it.

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