Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ft_author

Fetch a Financial Times contributor's public byline profile, including name, job title, email, social accounts, and recent articles by slug or URL.

Instructions

Get an FT author profile. Returns one Financial Times contributor's public byline profile (name, job title, email, social accounts) plus one page of their recent articles. FT author pages carry no bio paragraph, only this byline metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical www.ft.com/<slug> author URL; alternative to slug
pageNo1-based page number of the author's article list
slugNoAuthor URL slug, e.g. martin-wolf

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states what the response contains (byline fields and recent articles), and it discloses a key limitation: FT author pages have no bio paragraph. This is meaningful behavioral context, though it omits potential error/auth/rate-limit behavior.

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, with the core action front-loaded and every sentence adding value: what is returned, the pagination scope, and the absence of a bio paragraph. No filler or repetition.

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 simple read-only profile retrieval tool with no output schema and no annotations, the description provides the essential return-value information and a notable limitation. It does not explicitly state that one of url or slug is needed, but the schema's descriptions already imply that, so the overall package is reasonably complete.

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%, so the schema already documents url, slug, and page well. The description adds only a minor clarification that the article list is 'recent' and that one page is returned, which does not substantially improve on the schema's existing parameter descriptions.

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 an FT author profile.' It further specifies the exact output (byline metadata fields plus one page of recent articles), making the tool's purpose unmistakable and distinguishing it from sibling article/search tools.

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?

There is no guidance on when to choose this tool over alternatives such as ft_search, ft_article, or other publisher author tools. The description implies usage only through its purpose statement; it does not state when not to use it or name any alternative.

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