Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pcmag_author

Fetch a PCMag writer profile by slug or canonical URL to return name, role, biography, image, expertise topics, social links, and recent articles.

Instructions

Get a PCMag author profile. Returns a PCMag author profile by slug (for example michael-kan) or a pcmag.com authors url; supply exactly one. The response has name, role, biography, image_url, expertise topics linked to category hubs, social_links (X, LinkedIn, Bluesky, Threads) as full URLs, and recent articles.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical pcmag.com/authors/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. michael-kan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. 'Get' and 'Returns' imply a read-only operation and the response fields are listed, but there is no explicit statement of read-only safety, authentication needs, error behavior, or rate limits.

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?

The description is front-loaded and appropriately sized. It has minor redundancy in the opening two sentences ('Get a PCMag author profile. Returns a PCMag author profile...'), but overall every sentence contributes useful information.

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 simple profile lookup with no output schema, the description supplies the return fields, input constraints, and an example. It is nearly complete; only minor details like error behavior or pagination for recent articles are omitted.

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 is 3. The description adds the important exclusivity constraint ('supply exactly one') and an example slug, which go beyond the schema and help avoid misuse.

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?

The description states a specific verb and resource: 'Get a PCMag author profile.' It clearly distinguishes this tool from sibling PCMag tools like pcmag_article or pcmag_headlines, and from other outlets' author tools by naming PCMag.

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?

It gives clear input guidance ('supply exactly one' of slug or url), but does not state when to use this tool versus alternatives or provide any exclusions. Usage is implied by the purpose rather than explicitly addressed.

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