Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailyrecord_author

Fetch a Daily Record author profile by slug or canonical URL to retrieve name, job title, bio, email, X/Twitter link, and recent articles.

Instructions

Get a Daily Record author profile. Returns a Daily Record author profile, found by slug (for example paul-hutcheon) or by a canonical url; send exactly one of the two. The response has the name, job title, bio, email, X/Twitter link and recent articles with their label. Contact details the page does not list are simply absent.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical dailyrecord.co.uk/authors/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. paul-hutcheon

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 burden and does reasonably well: it enumerates the returned fields (name, job title, bio, email, X/Twitter link, recent articles) and discloses a behavioral edge case, that unlisted contact details are simply absent. It omits auth/rate-limit context and any explicit read-only statement, keeping it short of a 5.

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 tight sentences, front-loaded with purpose, then input modes, then return shape. Every clause earns its place with no redundancy or filler.

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?

No output schema exists, so the description correctly takes on return-value explanation, and it covers both input paths and the missing-contact-detail behavior. For a read-only profile lookup with zero annotations it is nearly complete, lacking only operational context like rate limits or pagination of 'recent articles'.

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% (baseline 3), but the description adds the mutual-exclusivity constraint 'send exactly one of the two' that the schema does not enforce (both params are optional with no required list), plus a concrete slug example (paul-hutcheon). That is genuine meaning beyond the structured fields.

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 (Daily Record author profile), and the name immediately disambiguates it from siblings like dailyrecord_article, dailyrecord_headlines and the many other *_author tools. An agent can tell exactly what it retrieves without opening the schema.

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 gives clear input-selection guidance ('send exactly one of the two') but never states when to reach for this tool over a sibling such as dailyrecord_article or cross-outlet author tools. It implies usage and constrains inputs, but provides no explicit when/when-not or named alternatives.

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