Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

standard_author

Fetch an Evening Standard author's public profile including name, job title, bio, X/Twitter handle, and recent articles. Supply a canonical URL or slug to get clean JSON.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical standard.co.uk/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. nicholas-cecil

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It conveys this is a read operation ('Get', 'Returns') and that the profile is 'public', implying no authentication is required. However, it does not disclose behavior around missing slugs, pagination of recent articles, or rate limits—gaps that are moderate for a simple profile fetch.

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 efficient sentences: the first front-loads the action and resource, the second lists the return fields. No filler, repetition, or extraneous detail.

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?

The description explains return values (helpful since there is no output schema) and the schema documents the parameters. However, it never states that at least one of `url` or `slug` must be provided even though both are marked optional in the schema, leaving an ambiguity for agents deciding whether zero-parameter calls are valid.

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%: both `url` and `slug` already have clear descriptions, including the canonical URL pattern, the example slug, and their relationship as alternatives. The tool description adds no parameter-specific semantics; baseline 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 states a specific verb ('Get'), a specific resource ('Evening Standard author profile'), and enumerates the returned fields (name, job title, bio, X/Twitter handle, recent articles). This clearly distinguishes it from sibling tools like standard_article or nzherald_author by naming the publication and the profile scope.

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 guidance is given about when to use this tool versus alternatives, such as standard_article or other author tools. The description implies 'use when you need an author profile' but provides no exclusions, prerequisites, or comparisons to sibling tools.

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