Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usmagazine_author

Fetch a Us Weekly author profile from a canonical author URL, returning name, biography, contact links, and the newest articles for research or editorial tracking.

Instructions

Get a Us Weekly author profile. Returns a Us Weekly author's profile from their canonical url (/author/<slug>/, required): name, biography, contact links and the newest articles, about 20. Staff and desk bylines may have no biography or links. Photo galleries are skipped and published_at is not set on the articles.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Us Weekly author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden: it describes returned fields (name, biography, contact links, about 20 newest articles), notes that staff/desk bylines may lack biography/links, and discloses that photo galleries are skipped and published_at is unset. It does not cover auth or rate limits, but its return and edge-case disclosure is strong for a read-only profile tool.

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 purpose and then dense with return and limitation details. No filler; every clause earns its place.

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 single-parameter author-profile endpoint with no output schema and no annotations, the description supplies return fields, article count, and known omissions. It is complete enough for correct invocation, though it could mention authentication if required.

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% and the single required url parameter is already documented. The description adds useful meaning beyond the schema by specifying the canonical path pattern `/author/<slug>/` and reiterating that it is required.

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?

States a specific verb ('Get') and resource ('Us Weekly author profile') and identifies the required input, so an agent can tell it retrieves an author profile rather than an article. It does not explicitly distinguish itself from sibling author/article tools, but the Us Weekly author scope is clear from the name and description.

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?

No when-to-use or when-not-to-use guidance is provided; it does not name alternatives such as usmagazine_article or other author tools. The required URL is mentioned, but that is a parameter constraint, not usage guidance.

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