Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wccftech_author

Retrieve a Wccftech author profile with name, role, bio, photo, and recent article cards by slug or author URL.

Instructions

Get a Wccftech author profile. Returns a Wccftech author profile with name, role, bio, photo and recent article cards (title, URL, summary, image, publication time). Identify the author with slug (such as sarfraz) or a canonical /author/<slug>/ url; one of the two is required.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical Wccftech author page URL
slugNoWccftech author slug, e.g. sarfraz

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only profile retrieval and describes returned fields, but it does not disclose pagination limits, article count, authentication needs, or other operational constraints.

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 description is front-loaded, uses three focused sentences, and includes no filler. It efficiently moves from purpose to return fields to input identification.

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?

For a two-parameter tool with no output schema and no annotations, the description covers the essential purpose, return shape, and identifier requirements. It could be more complete by specifying pagination behavior or handling for missing or duplicate identifiers.

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 baseline would be 3, but the description adds meaningful parameter semantics: a slug example and the canonical '/author/<slug>/' URL format. It also states that one of the two identifiers is required, which clarifies the schema's empty required list, though that creates a schema-description inconsistency.

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

Purpose4/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: 'Get a Wccftech author profile.' It also defines the returned content. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like wccftech_article or wccftech_news.

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?

The description gives parameter identification guidance ('slug' or 'url'; one required) but does not state when to use this tool versus alternatives. There is no explicit context, exclusion, or sibling comparison to guide selection.

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