Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

men_author

Fetch a Manchester Evening News author profile by URL or slug to get their name, job title, bio, email, X handle, and recent articles.

Instructions

Get a Manchester Evening News author profile. Returns one Manchester Evening News author's public profile: name, job title, bio, email, X/Twitter handle, and their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical manchestereveningnews.co.uk/authors/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. lee-swettenham

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 provided, the description carries the full burden. It transparently lists the returned profile fields and implies a read-only operation, but it does not disclose behavior when both optional parameters are omitted, error handling, or whether the email/handle fields are always present. This is adequate for a simple profile fetch but leaves some gaps.

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 with no filler. The core purpose is front-loaded, and the return fields are listed compactly. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool, the description covers the main purpose and return fields. However, both parameters are optional in the schema with no guidance that at least one is required, and there is no mention of what happens if neither is provided. The absence of an output schema is mitigated by the field list, but the parameter optionality gap remains.

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' parameters already described in the input schema. The description adds no additional parameter-level semantics, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Get a Manchester Evening News author profile.' It lists the exact fields returned (name, job title, bio, email, X/Twitter handle, recent articles), which clearly distinguishes it from sibling article/news tools like men_article or men_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?

The description makes it clear this is for retrieving a Manchester Evening News author profile, which is sufficient context for an agent to select it over article or news tools. However, it does not explicitly mention when not to use it or name alternative author tools, so it falls short of full exclusion 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