Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

standard_author

Retrieve an Evening Standard author profile by slug or canonical URL; returns name, job title, bio, X link, and recent articles with their sections.

Instructions

Get an Evening Standard author profile. Returns an Evening Standard author profile, found by slug (for example nicholas-cecil) or by a canonical url; send exactly one of the two. The response has the name, job title, bio, X/Twitter link and the author's recent articles with their section. It is one page, with no further pagination.

Input 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

A4.5/5.0
Behavior4/5

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

No annotations, so the description carries the burden and does well: it discloses the full response shape (name, job title, bio, X/Twitter link, recent articles with section) and explicitly states "one page, with no further pagination" — a behavioral trait not derivable from the schema.

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?

Three sentences, all front-loaded: identity, then selection rule, then return shape, then pagination note. Nothing redundant.

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?

For a two-param lookup with no output schema, the description covers invocation rules, return contents, and pagination limits — everything an agent needs to call it and interpret the result.

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%, so baseline is 3; the description adds the cross-parameter constraint (exactly one of slug/url) that the schema itself does not enforce, plus a slug format example. That is genuine value beyond the schema.

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+resource ("Get an Evening Standard author profile") and immediately pins down the identity mechanism (slug or canonical url). This clearly distinguishes it from sibling author tools for other outlets and from standard_article.

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?

Gives an explicit invocation rule ("send exactly one of the two") plus a concrete slug example, which is real selection guidance. It stops short of naming when to prefer this over standard_article / standard_headlines, so a 4 rather than 5.

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