Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

independent_author

Fetch an author profile from independent.co.uk by slug or URL to get bio, job title, X handle, and recent articles with titles, links, and sections.

Instructions

Get an Independent author profile. Returns one Independent author's profile by slug (for example lizzie-dearden) or url; exactly one is required. The response has name, job title, bio, X/Twitter handle and the author's recent articles with title, URL, section and section URL. It is a single page of articles with no further pagination.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical independent.co.uk/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. lizzie-dearden

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 well: it discloses the response shape (name, job title, bio, X handle, recent articles with section and section URL) and the key behavioral limit ('single page of articles with no further pagination'). It omits auth/permission or rate-limit context, which keeps 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?

Front-loads the purpose, then identifier rules, then return contents, then the pagination limit. Every sentence adds distinct information; no 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?

For a 2-param, annotation-free tool with no output schema, the description covers identity inputs, which-one-is-required, and the return payload including the no-pagination constraint. Only minor gaps (error behavior when an identifier is invalid) remain.

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 coverage is 100% and the schema already documents both parameters, including that url is an alternative to slug. The description largely restates this plus one concrete slug example, adding only marginal value over 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 and resource ('Get an Independent author profile') with explicit scope ('one Independent author's profile by slug or url'). Distinguishes itself from sibling article/news tools by focusing on the author entity, and names example identifiers.

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 a clear selection rule ('exactly one is required' of slug or url) and example slug, but never states when to prefer this over a related sibling like independent_article or independent_headlines, nor any preconditions. Context is clear, exclusions are absent.

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