Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newsweek_author

Retrieve a Newsweek author profile by slug or URL, including bio, image, email, job title, and paginated recent articles. Use page to control article pages.

Instructions

Get a Newsweek author profile. Returns a Newsweek author profile by slug (for example jennifer-fink) or a newsweek.com authors url; supply exactly one. page selects the 1-based page of recent articles (default 1) and overrides any page in url. The response has name, job_title, bio, email, image_url, articles and has_next_page; a page past the end gives an empty articles list, not an error.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical newsweek.com/authors/<slug> URL, optionally with a ?page=<n> query; alternative to slug
pageNo1-based page number; overrides any page number in url
slugNoAuthor slug, e.g. jennifer-fink

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the return fields (name, job_title, bio, email, image_url, articles, has_next_page) and the edge case that a page past the end gives an empty articles list, not an error. Missing details like rate limits or auth, but adequate.

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?

Two sentences, front-loaded with the core purpose, followed by key usage constraints and return information. Every sentence earns its place with no waste.

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?

Given no output schema and no annotations, the description must explain return values and behavior. It lists all fields returned, explains pagination edge cases, and clarifies parameter precedence. Complete for an agent to call correctly.

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%, so the schema already documents all three parameters. The description adds a mutual-exclusivity constraint ('supply exactly one') and an example slug, but the schema already states that url is an alternative to slug and that page overrides url's page. The added value is minimal.

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 and resource ('Get a Newsweek author profile'), and clarifies it returns a profile by slug or url. It is clearly distinguishable from sibling tools like newsweek_article and newsweek_headlines.

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?

Explains that exactly one of slug or url must be supplied and that page overrides any page in url. Provides clear context but does not explicitly name alternatives or when-not-to-use conditions.

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