Crawlora MCP

wccftech_author

Read-only

Retrieve a Wccftech author's public profile and recent story cards; provide exactly one author slug or canonical author URL.

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": "wccftech_author"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Canonical Wccftech author page URL
`slug`	No	Wccftech author slug, e.g. sarfraz

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.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / slug / description
```
Added value: +"Wccftech author slug, e.g. sarfraz"
```
- addedInput schema / properties / url / description
```
Added value: +"Canonical Wccftech author page URL"
```
First observedOct 5, 2026

TDQS

A4/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 what is returned ('public profile and recent story cards'), which is useful framing beyond the annotations, but it says nothing about pagination, rate limits, or how 'recent' is bounded.

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?

A single sentence, front-loaded with the action and resource, with the input constraint attached after the semicolon. No filler or repetition.

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?

An output schema exists, so return values need not be spelled out, and the description covers purpose, inputs, and their mutual exclusivity. Slightly short given it never clarifies what 'recent' means or whether a missing/invalid slug errors, but complete enough to call 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 100%, so the two parameters are documented in the schema. However, the description adds a constraint the schema does not encode: that exactly one of slug or url must be supplied (mutually exclusive, one required). That is genuine added meaning over the structured fields.

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 ('Retrieve') and resource ('Wccftech author's public profile and recent story cards'), which clearly separates it from the sibling wccftech_article, wccftech_headlines, wccftech_news and wccftech_sections tools. An agent can tell what this returns without opening the schema.

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 constrains inputs ('provide exactly one author slug or canonical author URL') but gives no explicit when-to-use or when-not guidance relative to siblings. Usage is implied by the tool name and the mention of 'author', so it is adequate but not directive.

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?