Crawlora MCP

wccftech_article

Read-only

Fetch public Wccftech article metadata and readable body paragraphs from a canonical url, including news, reviews, how-to guides, roundups, company posts, and best-of pages. Use wccftech_headlines to find stories, wccftech_sections to browse topics, or wccftech_news for the general feed.

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": {
      "url": "<url>"
    },
    "name": "wccftech_article"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical Wccftech article URL

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / url / description
```
Added value: +"Canonical Wccftech article URL"
```
First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that content is public and that readable body paragraphs are returned, but beyond that it offers little behavioral context (e.g. rate limits or truncation) and the output schema carries the return structure.

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?

Two tight sentences with the core purpose front-loaded and routing guidance second. No filler, though the long list of article types is slightly more than strictly necessary.

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

Completeness4/5

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

With an output schema, full schema coverage, and annotations covering safety and open-world behavior, the description supplies what is needed: a clear scope of content fetched and routing to sibling tools. Nothing essential is missing for correct invocation.

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?

Schema coverage is 100% with a single param whose schema description ('Canonical Wccftech article URL') matches the description's phrasing. The description restates but does not enrich it, so the baseline of 3 applies when the schema does the work.

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?

States a specific verb (Fetch) and resource (Wccftech article metadata and readable body paragraphs) with the required canonical url. It also enumerates the article types covered and names the sibling tools it is not, so an agent can distinguish it from wccftech_headlines/sections/news without opening their schemas.

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

Usage Guidelines4/5

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

Explicitly routes the agent: use wccftech_headlines to find stories, wccftech_sections to browse topics, wccftech_news for the general feed, implying this tool is for when a canonical article URL is already known. Clear alternatives are given, though there is no explicit 'do not call without a URL' statement.

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

All Crawlora MCP tools Inspect

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

Need Help?