Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

engadget_author

Fetch an Engadget author's public profile by slug or URL, returning their name, biography, expertise, social links, and recent stories.

Instructions

Get an Engadget author profile. Returns one Engadget author's public profile: name, biography, expertise, social links, and the latest stories listed on their page (a single fixed batch; the page has no further pagination).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical engadget.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. mariella-moon

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior itself. It notes the profile is 'public', implying no auth needed, and explicitly caps the stories at 'a single fixed batch' with 'no further pagination', which is valuable. It doesn't mention error behavior or invalid-slug handling, but it goes beyond a minimal description.

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?

Two sentences that front-load the action and resource, then list return fields and the pagination caveat. The second sentence's 'Returns one Engadget author's public profile' slightly restates the first, but there is no filler overall.

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?

With no output schema, the description compensates by naming the returned fields (name, biography, expertise, social links, latest stories) and the pagination limit. For a low-complexity read-only tool, this is enough for an agent to invoke it correctly, though error conditions are left unspecified.

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 description coverage is 100%, with both 'url' and 'slug' already described, so the description carries no additional parameter semantics. It correctly avoids repeating what the schema already documents.

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 ('Get') and resource ('Engadget author profile'), then enumerates the returned fields. The 'author' qualifier clearly distinguishes it from sibling tools like engadget_article or engadget_headlines.

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 establishes the tool's scope ('one Engadget author's public profile') and what it returns, so the intended use is clear. However, it never names an alternative or states when not to use it, leaving selection among the many sibling author tools to inference.

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